Skip to main content
Glama

Base Agent Due-Diligence Kit

Contract X-Ray teaser (free)

contract_xray_peek
Read-onlyIdempotent

FREE. Free teaser of Contract X-Ray: risk verdict headline and flag count for a token/contract address. The full report is the paid tool contract_xray.

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": {
      "address": "<address>"
    },
    "name": "contract_xray_peek"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain (default base)
addressYesContract address

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?

The annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds meaningful context beyond them: this is a deliberately truncated output (headline + count, not a full report) and a free tier gating a paid sibling — a behavioral trait no annotation conveys. It omits things like rate limits or confidence/coverage caveats of the verdict, keeping it below a 5.

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 sentences, front-loaded with the 'FREE' signal and ending on the routing pointer, which is the right order. Minor waste from restating 'FREE. Free teaser' — the redundancy costs a beat without adding information.

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 2-parameter, no-output-schema tool, the description covers what matters: what comes back (verdict headline + flag count), the input domain (contract address), and the relationship to the paid tool. The absence of an output schema makes describing the return shape especially valuable and it does so, though it says nothing about how a verdict is derived or how fresh it is.

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%, so both `address` and `chain` (with its enum and base default) are already documented in structured data. The description only restates 'for a token/contract address' and adds no format, normalization, or chain-selection guidance — baseline 3 is appropriate.

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 names a concrete verb+resource pair — 'risk verdict headline and flag count for a token/contract address' — and immediately distinguishes itself from its sibling contract_xray by scope and pricing tier. An agent can tell the teaser from the full report 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?

It explicitly names the alternative: 'The full report is the paid tool contract_xray,' which routes an agent that needs deeper analysis. What's missing is explicit when-to-use framing such as 'use this when you only need a quick verdict before paying' or any exclusion beyond the paywall distinction.

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