Skip to main content
Glama

docs_lookup

Look up a short, cited, versioned documentation snippet. The first 5 unpaid lookups per client IP per UTC day are free; after that this is a paid tool ($0.01 USDC on Solana via x402). Pass paymentSignature if you already have a signed payment; otherwise the result includes the 402 payment requirement. Optional ref (a Solana address) attributes the payer so the referrer can earn 10% of this agent's paid spend for 180 days, taken from the platform share.

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": {
      "q": "<q>"
    },
    "name": "docs_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesThe question or API name
refNoReferrer Solana address. First touch on a new payer sticks.
libraryNo
versionNo
paymentSignatureNoPAYMENT-SIGNATURE value from a prior x402 payment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the free tier (5 unpaid lookups per client IP per UTC day), the exact price ($0.01 USDC on Solana via x402), the 402 payment-requirement response path, and the referral payout mechanics. It omits whether the call is strictly read-only, what the snippet payload looks like, and any caching behavior.

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?

Purpose is front-loaded in the first sentence, followed by pricing, payment mechanics, and referral attribution in a logical order. The referral-economics sentence is somewhat long, but every piece conveys information the agent needs before paying.

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

Completeness3/5

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

For a paid, no-annotation, no-output-schema tool this covers the critical payment and rate-limit paths well. However, it leaves library and version undefined anywhere in the definition, and with no output schema the agent gets only a vague sense ('short, cited, versioned snippet') of what comes back.

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?

Schema coverage is 60%, and the description adds real meaning for two parameters: paymentSignature is explained through the alternate 402 outcome, and ref is explained in depth (attributes the payer, 10% of paid spend for 180 days from the platform share). The library and version parameters remain unexplained in both the schema and description.

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?

Names a specific verb and resource ('Look up a short, cited, versioned documentation snippet'), which is clearly distinguishable from docs_contribute and docs_verify by intent. It stops short of explicitly differentiating itself from siblings such as docs_libraries, so it falls just under a 5.

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

Usage Guidelines2/5

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

There is no when-to-use/when-not-to-use guidance and no mention of alternatives for narrowing to a library or version instead. The only conditional language concerns how to pay ('Pass paymentSignature if you already have a signed payment'), which is invocation mechanics rather than tool-selection guidance.

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.

Resources