Skip to main content
Glama

full_report_info

Read-only

Free. How to buy the full report (paid MCP tool full_report or HTTP GET /v1/check, 0.25 USDC via x402 on Base). Does not pay.

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": "full_report_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds meaningful behavioral context beyond that: it is free, it does not execute payment, and the paid path involves 0.25 USDC on Base via x402. It is consistent with the read-only annotation and usefully prevents the agent from assuming a transaction occurs.

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?

Three short fragments with zero filler, front-loaded with the key fact ('Free.') and ending with the crucial exclusion ('Does not pay.'). The telegraphic style is efficient, if slightly clipped for an unsupervised reader.

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, no-output-schema info tool, the description covers what an agent needs: it is free, it does not pay, and where the paid path lives. The only minor gap is not stating that it returns instructional text, but the shape of the tool makes that inferable.

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 schema is empty with 100% coverage, so the baseline applies. There is nothing for the description to disambiguate about inputs, and none is needed.

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 states this is a free informational tool explaining how to obtain the full report, and names the paid sibling (full_report) plus the HTTP equivalent. It distinguishes itself from full_report clearly, though the phrasing is terse and reads more like a price note than a purpose statement.

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

Usage Guidelines4/5

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

It explicitly points to the alternatives (full_report MCP tool or HTTP GET /v1/check) and states the cost path (0.25 USDC via x402 on Base), while 'Does not pay' rules out the mistaken expectation that calling this performs payment. That is clear when-to-use and when-not context, though it never says outright 'call this first if you need purchase instructions'.

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.