mcphost

host.help.search

Search this host's own documentation and tool descriptions. Returns up to k hits (default 3, response under 2 KB), each with a snippet, the nearest runnable example and an anchor. Read-only, anonymous, no tenant data -- call it with the error text or import line you are stuck on before reading any docs file.

Input Schema

TableJSON Schema

Name	Required	Description
`k`	No	How many hits to return (default 3).
`q`	Yes	What you are stuck on: a tool name, an error code or message, an import line.
`kind`	No	Only search the page of this registered kind (docs/kinds/<kind>.md).
`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
`hint`	No
`hits`	Yes
`total`	Yes
`index_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / kind / enum

Previous value: -[
-  "chain",
-  "echo",
-  "http",
-  "js",
-  "python",
-  "wasm"
-]New value: +[
+  "chain",
+  "echo",
+  "http",
+  "jq",
+  "js",
+  "python",
+  "wasm"
+]

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / kind / enum

Previous value: -[
-  "chain",
-  "echo",
-  "http",
-  "python",
-  "wasm"
-]New value: +[
+  "chain",
+  "echo",
+  "http",
+  "js",
+  "python",
+  "wasm"
+]

Changed4 schema fields changedOct 16, 2026
- changedOutput schema / properties / hint / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / hits / items / properties / example / properties / truncated / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / hits / items / properties / example / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / hits / items / properties / next_tool / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
AddedOct 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden and meets it: read-only, anonymous, no tenant data, capped at k hits, response under 2 KB, and each hit returns a snippet, the nearest runnable example and an anchor. Safety profile, blast radius and result shape are all disclosed without needing the schema.

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 the verb and resource, then result shape, then safety, then the usage trigger. No clause is redundant — even the size cap and hit contents earn their place.

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

Completeness5/5

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

An output schema exists, so return values need no prose. The description still covers purpose, safety, size limits, hit payload and the invocation trigger, leaving nothing an agent needs in order to call this correctly.

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 documents q, k, kind and tenant_key (including the enum and the tenant-binding rule). The description restates the k default of 3 and the 2 KB cap but adds no syntax or selection guidance for kind or tenant_key, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource with scope: 'Search this host's own documentation and tool descriptions.' That cleanly separates it from host.help.get (fetch a specific page), host.quickstart (onboarding flow) and host.whoami (identity), so an agent can pick it without opening any schema.

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 a concrete trigger and ordering rule: 'call it with the error text or import line you are stuck on before reading any docs file.' That is clear when-to-use plus an implicit when-not (don't read docs files first). It stops short of naming host.help.get as the alternative, so it is strong but not fully explicit routing.

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.