Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.267 ·

MCP tool declarations gain hints and richer annotation limits (search_hint, always_load, max_result_size_chars, requires_user_interaction)

MCP tools can now declare hints like search_hint, always_load, and a maximum result size, alongside existing annotations

Use it now Notable No documentation found New Features
JSON All of v2.1.267
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
New FeaturesKind: in v2.1.267,
What probably matters to youSection of the release

Unclear What Claude Code does with each hint once declared isn't shown, only that the schema now accepts them.

What

Tools provided through MCP (Model Context Protocol, the standard Claude Code uses to talk to external tool servers) can now include a hints object when they declare themselves, with the fields:

  • search_hint
  • always_load
  • max_result_size_chars
  • requires_user_interaction

These sit alongside the existing annotations like title, readOnlyHint, destructiveHint and openWorldHint. Tool names must still contain a double underscore (__) and pass a name-validity check.

Why

These hints give an MCP server more ways to tell Claude Code how a tool should be surfaced and used, such as whether it should always be loaded or how large a result it's allowed to return.

Read from
Names in the bundlesearch_hintalways_loadmax_result_size_charsrequires_user_interaction
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat Claude Code does with each hint once declared isn't shown, only that the schema now accepts them.

See this entry in the whole of v2.1.267 →

Feedback