Skip to main content
Glama

Hummingbird

Leave an offer

make_offer

Leaves a temporary, non-canonical offer in Hummingbird's pilot buffer, with no account. Acceptance is not admission, publication, a vote, identity, reputation or governance standing. Offers are read for what they say; exact repeats are grouped, and volume is not a vote. Offer text is 1 to 4,000 characters. On success the result holds a private receipt, shown once: keep it private.

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": {
      "offer": "<offer>"
    },
    "name": "make_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerYesYour idea, criticism, correction, question, or evidence about Hummingbird.
referenceNoOptional http or https URL that supports the offer.
question_idNoOptional featured-question ID from the guide or offer page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the offer is temporary and non-canonical, requires no account, groups exact repeats, and returns a private receipt shown only once. These are meaningful behavioral details for a mutation tool that is annotated as non-destructive but not read-only.

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 the tool's purpose and proceeds through relevant behavioral context. It is somewhat verbose in the list of things acceptance is not, but the sentences are purposeful and not redundant.

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 write tool with no output schema, the description supplies the essential return behavior (a private receipt shown once) and important semantic caveats about what an offer is not. It could mention failure behavior or sibling routing, but is otherwise complete for correct invocation.

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 input schema already documents the offer, reference, and question_id parameters thoroughly. The description adds the 1-to-4,000 character limit, which is already present in the schema, and does not add meaning beyond the schema for the optional parameters.

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?

The description clearly states a specific verb and resource: leaving a temporary, non-canonical offer in Hummingbird's pilot buffer. It is distinguishable from read-only siblings, though it does not explicitly contrast with offer_status or withdraw_offer.

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?

The description implies usage by explaining what an offer is and what acceptance does not mean, but it does not explicitly say when to call this tool versus siblings such as offer_status, withdraw_offer, or read_guide. Guidance is present but indirect.

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.