mcphost

host.help.get

Return the documentation section an anchor points at: its text (at most 4 KB) and its first fenced example. Pass an anchor exactly as an error, hint or help entry printed it, e.g. a rate_limited error's anchor. Read-only, anonymous, no tenant data. An unknown anchor is anchor_not_found with the nearest anchors in did_you_mean.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`anchor`	Yes	A `<path>#<slug>` anchor, e.g. README.md#call-limits, as printed by an error's `anchor` field or a `host.help.search` hit. `<path>#top` and a bare `<path>` (e.g. docs/kinds/chain.md) both return that document's first section.
`tenant_key`	No	The key `signup` returned. Optional on the connection that ran signup (or host.redeem): that connection is already bound to the tenant it created, so later calls on it need no tenant_key. On a connection with no Authorization: Bearer header and no prior signup, omitting it implicitly signs that connection up as a brand-new tenant and runs this call as it -- see host.whoami's source field. When both a header and this argument are present, the header wins.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`line`	Yes
`path`	Yes
`text`	Yes
`title`	Yes
`anchor`	Yes
`example`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / anchor / description

Previous value: -"A `<path>#<slug>` anchor, e.g. README.md#call-limits, as printed by an error's `anchor` field or a `host.help.search` hit."New value: +"A `<path>#<slug>` anchor, e.g. README.md#call-limits, as printed by an error's `anchor` field or a `host.help.search` hit. `<path>#top` and a bare `<path>` (e.g. docs/kinds/chain.md) both return that document's first section."

Changed1 schema field changedOct 16, 2026
- changedOutput schema / properties / example / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
AddedOct 15, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does well: it discloses read-only, anonymous, no-tenant-data behavior, the 4 KB truncation cap, and the failure mode ('an unknown anchor is anchor_not_found with the nearest anchors in did_you_mean'). It omits one notable side effect documented only in the schema: omitting tenant_key on an unauthenticated connection implicitly signs up a new tenant, which sits awkwardly beside 'anonymous, no tenant data'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with what is returned, then how to call it, then the safety/error profile. Zero filler and no restatement of the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't explain return values, and it still summarizes them usefully; for a 2-parameter tool this is close to complete. The only substantive omission is the implicit-signup behavior of omitting tenant_key, which lives solely in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already defines both parameters in depth; the baseline is 3. The description reinforces the anchor's expected form ('exactly as an error, hint or help entry printed it') but says nothing about tenant_key and adds no syntax beyond what the schema gives.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Return the documentation section an anchor points at') plus the exact payload shape ('its text (at most 4 KB) and its first fenced example'), which is far more precise than the tool name alone. The contrast with host.help.search is only implicit via the anchor-shaped input rather than stated, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real invocation context: 'Pass an anchor exactly as an error, hint or help entry printed it, e.g. a rate_limited error's `anchor`', telling the agent where anchors come from. It never names host.help.search as the way to find an anchor you don't already have, and gives no explicit when-not guidance, so it is clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcphost tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.