Skip to main content
Glama

contract_monitor

Read-onlyIdempotent

Monitor recent contract activity for suspicious admin operations, proxy upgrades, ownership changes, and pause events. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain networkethereum
addressYesContract address
lookbackHoursNoHours to look back (max 168)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: a free tier of 10 calls per day and, past that, a fallback that returns a pay-per-call x402 endpoint and its price. That kind of quota/rate-limit disclosure is exactly the extra value the bar asks for. It does not describe the shape of the activity results, which keeps it from 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.

Conciseness5/5

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

Two sentences: the capability and its detection targets come first, the cost/quota caveat second. No filler, no repetition of the name or schema, and the most decision-relevant constraint is front-loaded.

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 simple three-parameter read tool with full schema documentation and complete annotations, the definition covers purpose, scope, and the quota fallback. The main remaining gap is that with no output schema, the agent is not told what the monitor returns (an event list? a risk verdict?), which matters for a monitoring tool. Otherwise an agent has enough to invoke it correctly.

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% — chain (with enum), address, and lookbackHours (with bounds and default) are all documented in the schema. The description adds no parameter-level meaning such as what counts as 'recent' or how the chain selection affects coverage, so the baseline of 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 uses a specific verb ('Monitor') plus resource ('recent contract activity') and enumerates the concrete event classes it surfaces: admin operations, proxy upgrades, ownership changes, pause events. That is far more specific than a tautology. It stops short of naming how it differs from siblings like address_check, contract_docs, or risk_batch, so it does not reach a 5.

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 is implied by the enumerated event types (use it when you want to watch a contract for privileged changes), but there is no explicit when-to-use statement, no prerequisites, and no routing to or away from the many sibling scanners. The quota note tells the agent about cost after 10 calls, which is helpful context but not selection guidance.

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.