Skip to main content
Glama

edge-signals

token_verdict_before_buy

Graded token due-diligence ($0.01): letter grade A–F, SAFE|CAUTION|AVOID band, score 0–100, reasons and metrics. Richer than token-risk before buy, bridge, or treasury allocation.

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": {
      "token": "<token>"
    },
    "name": "token_verdict_before_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase (default), ethereum, bsc, arbitrum, optimism, polygon
tokenYesERC20 contract
addressNoAlias for token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 disclose two important behavioral traits: the $0.01 cost and the exact shape of what is returned (grade, band, score, reasons, metrics). It omits whether the call is read-only, any rate limits or latency expectations, and failure behavior for unsupported tokens, which keeps it below the top mark.

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?

Two compact segments: purpose plus output payload first, then the comparative positioning. Every clause conveys new information, though the colon-list of output fields is dense enough that the sentence has to be re-parsed once.

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 return components, so an agent knows what it gets for $0.01. For a three-parameter, fully documented read-style analysis tool this is largely complete; only cost/benefit routing versus the sibling is left somewhat implicit.

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%, including the chain enum-style list with a stated default and the note that address is an alias for token, so the schema already does the heavy lifting. The description adds no parameter-level detail beyond it, which is the expected baseline here.

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?

The description gives a specific verb and resource ("graded token due-diligence") and immediately enumerates the output artifacts: letter grade A–F, SAFE|CAUTION|AVOID band, score 0–100, reasons and metrics. It also names the closest sibling (token-risk / token_risk_before_buy) and claims superiority, so an agent can distinguish the two without opening either schema.

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?

The phrase "before buy, bridge, or treasury allocation" names concrete decision contexts where this tool applies, and "richer than token-risk" implies the trade-off against the cheaper sibling. It stops short of stating when NOT to use it or when the lighter alternative is preferable despite the extra cost.

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