Skip to main content
Glama

research_report

Paid $0.50 full / $0.10 preview (x402, USDC Base): LLM 70B writes a structured 7-section research report on your question — executive summary, market context, key data grounded in LIVE prices + Fear & Greed + headlines, bull case, bear case, watchlist, bottom line. Optional arg address (0x...) grounds it in live Base token on-chain verdict. Always delivers a data-grounded report even if AI prose is unavailable. Args: topic (string), address (optional), lite (boolean = $0.10 preview).

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

Input Schema

NameRequiredDescriptionDefault
liteNotrue = $0.10 preview (executive summary + top signal)
topicNoResearch question, e.g. 'Is the Base ecosystem still early?'
addressNoOptional Base token 0x... to ground in live on-chain data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the payment requirement (x402, USDC on Base), exact prices, and a degradation guarantee ('Always delivers a data-grounded report even if AI prose is unavailable'). It leaves out how the agent is expected to complete payment after a 402 and what latency or failure modes to expect.

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 pricing and value proposition are correctly front-loaded and the section list is compact. The trailing 'Args:' sentence largely echoes the input schema and could be dropped without loss.

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?

There is no output schema, and the description compensates by enumerating the seven returned sections; with no annotations, it also discloses cost and the fallback behavior. The remaining gap is the mechanics of the paid x402 handshake, which an agent needs to actually complete a call.

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 coverage is 100%, so the baseline is 3. The description adds only modest meaning beyond the schema — restating topic/address/lite and clarifying that address triggers a live Base on-chain verdict — which is close to what the schema already conveys.

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?

States a specific verb and artifact: an LLM writes a structured 7-section research report, with sections enumerated and an optional on-chain grounding mode. An agent can distinguish this from siblings like ai_chat, get_market_pulse, or get_token_verdict because the description defines the output shape and the data sources it fuses.

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 pricing tiers imply the choice between the full $0.50 report and the $0.10 lite preview, and the address argument implies when to use the on-chain variant. However, it never says when to prefer this over the sibling tools that supply the same underlying data (get_token_verdict, get_market_pulse, get_crypto_news) or when a paid report is not warranted.

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