Skip to main content
Glama

Base Agent Due-Diligence Kit

Solidity Red-Flag Scan teaser (free)

solidity_scan_peek
Read-onlyIdempotent

FREE. Free teaser of the Solidity Red-Flag Scan: which verified source files were found (Sourcify) and how many rules hit. Full findings: solidity_red_flag_scan.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain (default base)
addressYesVerified contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds real value by disclosing that output is deliberately truncated (file list plus rule counts only), but says nothing about rate limits, quota, or cost beyond 'FREE' for this call.

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/teaser framing, and the escalation path is placed last where it belongs. Minor waste in restating 'FREE' twice in the opening.

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 carries the return-value burden and does say what comes back (files found, number of rule hits). For a two-parameter read-only teaser this is nearly sufficient; only output shape and any quota behavior are left 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 coverage is 100%, with the address pattern, chain enum and default base already documented. The description adds no extra meaning about the chain or address parameters, so the baseline 3 applies.

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 resource: returns which verified source files were found (Sourcify) and how many rules hit. It explicitly names the full-findings sibling, 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?

Makes the preview-vs-full split explicit by pointing to solidity_red_flag_scan for complete findings, which conveys when to escalate. It does not state any exclusions or prerequisites (e.g., that a verified source must exist), leaving a small gap.

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