Honeydew AI Documentation

Search documentation

search_honeydew_documentation

Read-onlyIdempotent

Search across the Honeydew Documentation knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Honeydew Documentation, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to head or cat the page path (append .mdx to the path returned from search — e.g. a result at /some/page is read with head -200 /some/page.mdx).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_honeydew_documentation"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 19, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedMay 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description need not re-explain safety. It adds useful behavioral context beyond annotations by describing the return shape as contextual content with titles and direct documentation links, and by documenting the .mdx path convention needed to retrieve full page content via the sibling tool.

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

Conciseness4/5

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

The description is front-loaded with purpose and usage, then moves into return behavior and the sibling-tool handoff. It is slightly long but every sentence carries actionable information, particularly the .mdx path example.

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?

Complete for a one-parameter search tool: it explains what the tool finds, when to use it, what it returns in broad terms, and exactly how to move from a search result to full page content. No output schema exists, and the description sufficiently covers the relevant return characteristics without overclaiming structure.

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?

There is only one parameter, query, and schema description coverage is 100%, so the schema already explains it adequately as 'Search query'. The description does not add query syntax, formatting guidance, or examples beyond the workflow for reading results, so baseline 3 is appropriate.

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: searching across the Honeydew Documentation knowledge base for information, code examples, API references, and guides. The scope is clear enough that an agent can distinguish it from the filesystem-reading sibling without inspecting schemas.

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

Usage Guidelines5/5

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

Explicitly names when to use it: answering questions about Honeydew Documentation, finding specific docs, understanding features, or locating implementation details. It also names the alternative for full page content and gives the exact handoff pattern: use query_docs_filesystem_honeydew_documentation with head/cat and append .mdx.

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

All Honeydew AI Documentation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?