Skip to main content
Glama

Escrow contract reference

get_usdc_escrow_contract
Read-onlyIdempotent

Returns the reference data for AgentSLA's escrow contract on Base Mainnet: contract and USDC token addresses, chain id, the pass price and period, the 2% escrow fee, the 7-day reclaim timeout, the human-readable ABI of the functions agents call, and a Basescan link. Use it to verify the addresses that buy_pass and create_escrow_job put in their transactions. Free, read-only, static.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description adds useful context beyond that by labeling the data static and free and by listing the exact values returned, which tells the agent the call is cheap and safe to repeat. It slightly restates read-only from the annotations but the 'static' and 'free' framing is additional information.

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?

The payload enumeration is front-loaded in the first sentence, followed by a single usage sentence and three short qualifiers. Every clause earns its place, with only minor redundancy in 'read-only' echoing the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing return values, and it does so field by field, including the ABI and Basescan link. Combined with the annotations and the zero-parameter schema, an agent has everything needed to call it correctly and interpret the result.

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 meaning to add; the schema is empty and closed (additionalProperties=false), matching the description's implication of a parameterless lookup. Baseline 4 applies for a no-parameter tool.

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?

The description gives a specific verb ('Returns') and resource ('reference data for AgentSLA's escrow contract on Base Mainnet') and then enumerates the exact payload: contract and USDC token addresses, chain id, pass price/period, 2% fee, 7-day reclaim timeout, ABI, and Basescan link. This is unmistakably a static-config lookup and cannot be confused with the sibling job/pass tools.

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 states a concrete when-to-use case: verify the addresses that buy_pass and create_escrow_job put in their transactions, naming two siblings explicitly. There is no explicit when-not or statement of what to use instead for other reference needs (e.g. get_api_details), so it falls short of full routing 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.

Resources