Skip to main content
Glama

Contract flags

contract_flags

What can the owner of a contract on Base or Arc do to holders? Mint, pause, blacklist, fees, limits, trading switch, upgradeable proxy, and who owns it, read from the bytecode. $0.004 per call over x402.

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

Input Schema

NameRequiredDescriptionDefault
chainYesbase or arc
addressYesthe contract address (0x...)
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does carry extra context: it discloses that findings come from static bytecode analysis, that it is Base/Arc-only, and that each call costs $0.004 via x402. It does not state that results are heuristic/static (so admin powers set post-deploy or in proxies may be missed), nor latency or failure modes — meaningful gaps for a risk tool with zero annotation coverage.

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 sentences: the capability question and flag list come first, pricing last. Every clause carries information, though the question-style opening is slightly less direct than a declarative verb+resource statement.

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 3-parameter read tool with no output schema, the description usefully enumerates the flags returned and explains the paid-call model alongside the schema's payment parameter. The remaining gap is not specifying the response shape (boolean flags vs. owner address vs. proxy target), which the absence of an output schema leaves to inference.

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 'base or arc', the 0x address, and a detailed x402 payment explanation, so the schema already does the work. The description adds only the price figure and confirms the bytecode source; it contributes nothing new about the chain or address parameters. Baseline 3 applies.

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?

The description states a concrete analysis task (surfacing owner powers on a Base/Arc contract) and enumerates the specific flags detected: mint, pause, blacklist, fees, limits, trading switch, upgradeable proxy, ownership. That is well beyond the tautological title and clearly separates it from a plain bytecode/read tool. It stops short of 5 because it is framed as a rhetorical question and never explicitly contrasts itself with near-neighbours like arc_contract_check or arc_token_check.

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?

Use is only implied: asking 'what can the owner do to holders' signals a pre-interaction due-diligence check, but there is no explicit when-to-use, no when-not-to-use, and no named alternative among the many contract/token screening siblings. An agent must infer the selection rule from the flag list.

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