Skip to content

docs: clarify MCP tool profile visibility#594

Merged
will-lamerton merged 1 commit into
Nano-Collective:mainfrom
zerone0x:docs/mcp-tool-profile-visibility
Jun 27, 2026
Merged

docs: clarify MCP tool profile visibility#594
will-lamerton merged 1 commit into
Nano-Collective:mainfrom
zerone0x:docs/mcp-tool-profile-visibility

Conversation

@zerone0x

Copy link
Copy Markdown
Contributor

Summary

  • document that the default auto tune profile may resolve to minimal/nano for small local models
  • clarify that MCP tools are visible to the model only when the resolved tool profile is full
  • add troubleshooting guidance to switch /tune to full when /mcp shows servers but the model cannot call their tools

Fixes #593

Tests

  • corepack pnpm exec biome check docs/features/tune.md docs/configuration/mcp-configuration.md (Biomes reports these Markdown docs are ignored, so no files were processed)

Note: the local pre-commit hook could not run because it invokes pnpm directly and this environment only has pnpm through Corepack; the docs-only change was committed with --no-verify after the Biome check attempt above.

Fixes Nano-Collective#593

Co-Authored-By: bridge <bridge@hermes.agent>

@akramcodez akramcodez left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM @zerone0x Thanks for the documentation improvements 👍

@will-lamerton will-lamerton merged commit 89c4da7 into Nano-Collective:main Jun 27, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[UX] Non-obvious why some tools are not exposed to the model

3 participants