Skip to main content
Glama

Inspect Tereno's ERC-7579 Modular Guard Hook

tereno_erc7579_module

Free. Get the deployed address (0x7579c4a8E161C689d71c4c8A72B8D361F89C402E on Base), ABI, supported smart account architectures (Safe, Biconomy, Kernel) and pre-action verification configuration for the ERC-7579 Guard Hook.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tereno_erc7579_module"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add genuinely useful context: the call is free, the deployment is on Base, and the exact address is given, which signals a static metadata read. However, it says nothing about whether results are cached, whether the address can change, or what happens for unsupported chains.

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?

A single well-formed sentence with the cost note front-loaded and no wasted clauses. The embedded contract address and chain are dense but relevant rather than filler.

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 must enumerate the returned payload, and it does so concretely: address, ABI, supported account architectures, and verification configuration. For a simple zero-parameter lookup this is close to sufficient, with only provenance or freshness details missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 clear verb-and-resource framing ('Get the deployed address, ABI, supported smart account architectures and pre-action verification configuration for the ERC-7579 Guard Hook'), so an agent knows exactly what data comes back. It does not distinguish this from siblings such as contract_guard or tereno_catalog, which plausibly overlap, so it stops short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus the other guard or catalog tools; the only usage-relevant signal is the leading 'Free.' cost note. An agent must infer that this is the right entry point for ERC-7579 module inspection from the name alone.

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.