Skip to main content
Glama

Honeydew AI Documentation

by ai.honeydew

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. head -200 /api-reference/create-customer.mdx).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds no additional behavioral traits beyond confirming it returns search results. Since annotations already provide transparency, the bar is lower, and the description is consistent but adds no new context.

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 concise and well-structured with three sentences. It covers purpose, usage, and an alternative tool without unnecessary fluff. It is slightly longer than the minimal two sentences but remains efficient and clear.

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?

The description sufficiently covers the tool's purpose, usage scenarios, output (contextual content with titles and links), and points to a complementary tool for full content. Given no output schema, it adequately describes what the user can expect. The context is complete for a read-only search tool.

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?

The only parameter 'query' has a schema description 'Search query' which is straightforward. The tool description does not elaborate further on the parameter, but schema coverage is 100%, so the baseline is acceptable. No additional meaning is provided beyond the schema.

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?

The description clearly states the tool's function: searching across Honeydew Documentation to find relevant information, code examples, API references, and guides. It also specifies the output (contextual content with titles and links), making the purpose unambiguous.

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?

The description explicitly states when to use the tool ('when you need to answer questions about Honeydew Documentation, find specific documentation, understand how features work, or locate implementation details') and provides an alternative tool ('use the query_docs_filesystem tool') for full page content, giving clear guidance on usage scenarios.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

The two main tools are clearly distinct: one performs filesystem-style queries on a virtual documentation tree, and the other is a semantic search over the knowledge base. The third tool, feedback submission, is entirely different in purpose. The only minor ambiguity is that the search tool and filesystem tool both retrieve documentation, but their descriptions clarify different use cases.

Naming Consistency3/5

Tool names are descriptive but not uniformly patterned. 'query_docs_filesystem_honeydew_documentation' uses verb-object with a suffix, 'search_honeydew_documentation' uses verb-noun, and 'submit_feedback' is a simple verb-noun. The inconsistency lies in the inclusion of the server name in some but not all, and the length of the first name is cumbersome, but the verbs are clear.

Tool Count4/5

Three tools is on the lean side but appropriate for a documentation assistant: one for structured file-system access, one for semantic search, and one for feedback. It avoids unnecessary redundancy and covers the core need. Slightly more could be added (e.g., a dedicated get_page tool), but the count is reasonable.

Completeness4/5

The tool set covers the essential workflows: searching for information, reading specific pages, and reporting issues. The filesystem tool can simulate file browsing and reading, which compensates for the lack of a dedicated 'get page' tool. A minor gap is the absence of a tool to list all pages or navigate with more advanced filters, but agents can work around this with tree/ls and rg.

Resources