Skip to main content
Glama

Token research pack

research_pack
Read-onlyIdempotent

Get a deterministic due-diligence report with evidence for every claim and explicit coverage gaps. Paid HTTP offer: $5.00 USDC. This tool returns free x402 payment requirements; it does not execute or pay for the offer.

Input Schema

NameRequiredDescriptionDefault
chainYesNetwork of the input; payment is always USDC on Base.
tokenYesBase ERC-20 contract address or Solana mint; must match chain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Adds behavior the annotations cannot convey: the offer costs $5.00 USDC, the call itself is free, it returns x402 payment requirements, and it does NOT execute or pay for the offer. This two-step flow is exactly the kind of fact an agent would otherwise get wrong on first invocation, and it is consistent with readOnlyHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what the agent gets, followed by price and the crucial non-execution caveat. No filler or repetition.

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?

With no output schema, the description correctly tells the agent that the immediate return is payment requirements rather than the report, which is the key completeness requirement here. It stops short of describing what the paid report contains or how to complete payment and re-invoke, leaving a modest gap for a paid, multi-step tool.

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%, with both chain and token documented including the chain-matching pattern, so the schema carries parameter meaning. The description adds nothing parameter-specific beyond noting payment is always USDC on Base, which the chain field already states.

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?

States a specific verb and resource: a deterministic due-diligence report with per-claim evidence and disclosed coverage gaps. That distinguishes it in substance from a verdict-style sibling, though the description never names an alternative, so an agent must infer the boundary itself.

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?

Usage context is implied (due diligence on a token) and the payment flow is clarified, but there is no explicit statement of when to pick this over token_verdict or wallet_risk, and no prerequisites or exclusions beyond the cost note.

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