Skip to main content
Glama

Hummingbird

Read the Hummingbird guide

read_guide
Read-only

Returns Hummingbird's machine-readable guide (llms.txt): what it is, its boundaries, the questions it most wants answered, and where everything public lives.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds that the return is a static machine-readable guide document rather than live service data, but says nothing about size, whether it is cached, or how it relates to subsequent calls — modest added context over the annotations.

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?

A single front-loaded sentence identifying the resource, its format (llms.txt), and its contents — no repetition or filler. The phrases "the questions it most wants answered" and "where everything public lives" are evocative rather than precise, which slightly reduces informational density.

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?

For a zero-parameter, read-only, non-open-world tool with no output schema, the description covers what is returned at a topical level. It could go further by saying the guide is the canonical starting point for discovering the service's other capabilities, but nothing essential to invoking it correctly is missing.

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

Parameters4/5

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

The tool takes zero parameters and the description makes no confusing parameter claims, so the baseline of 4 applies. Nothing in the description misrepresents how the call is made.

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?

"Returns Hummingbird's machine-readable guide (llms.txt)" names a specific verb and resource, and the clause that follows enumerates the guide's contents (boundaries, intended questions, where public resources live). That is enough for an agent to know this is a documentation/orientation read, and the sibling set (records, offers) is unrelated enough that no explicit contrast is needed.

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

Usage Guidelines3/5

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

Purpose implies usage (read this to learn what Hummingbird is and where things live), but there is no explicit when-to-use instruction such as "call this first before other tools" and no stated alternative. The agent must infer that this is an onboarding/discovery call from the content description alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.