Skip to main content
Glama

Contracts

get_contracts
Read-onlyIdempotent

Every Semiosis contract on Robinhood Chain (chain id 4663) with its role and explorer link, and the outside contracts it uses: among them Semiosis’s Pons launch curve (outside, key ponsCurve), the to of a trade routed to Pons, which is Pons’s own contract and not verified on the explorer. Check a transaction’s to against this list before signing it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add context — which it does by disclosing the chain id, that entries include roles and explorer links, and crucially that some listed contracts (Pons's own `to` target) are external and not verified on the explorer. That last point is a real behavioral caveat an agent could not infer from the annotations. It does not describe ordering, caching, or completeness guarantees, so it is not 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.

Conciseness3/5

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

The intent is front-loaded in the opening clause, but the middle is overpacked: the nested '(outside, key ponsCurve)' aside and the halting 'the `to` of a trade routed to Pons, which is Pons's own contract and not verified on the explorer' force re-reading. The closing imperative is well placed, but the body could be restructured into two clean sentences without losing content.

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 burden of saying what comes back, and it does — roles, explorer links, and both first-party and external contract sets. For a zero-parameter read tool that is close to sufficient. A brief note on how entries are keyed (address vs. name, and the meaning of `ponsCurve`) would have closed the remaining gap.

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 schema semantics for the description to compensate for; the baseline for a parameterless tool applies. Nothing in the description contradicts or misuses the empty input object.

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 names a concrete resource — every Semiosis contract on Robinhood Chain (chain id 4663) — and states what each entry carries (role and explorer link), plus that outside contracts like the Pons curve are included. That is far more specific than a name restatement. It loses a point because the sentence structure is tangled, with the Pons parenthetical and 'the `to` of a trade routed to Pons' interrupting the core list-both-contract-sets statement.

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 gives an explicit, actionable trigger: 'Check a transaction's `to` against this list before signing it.' That tells the agent exactly when to reach for this tool relative to a signing step. It stops short of naming a sibling alternative or describing when not to use it, so it is not a full when/when-not treatment.

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