Skip to main content
Glama

Register escrow terms

register_escrow_terms
Idempotent

Records the latency limit for an escrow job after its createJob transaction confirms, so the oracle knows the SLA to judge. Use it once per job, right after the create_escrow_job transactions. The job is read from the transaction on Base; only its creator's transaction is accepted, and the first registration is kept (calling again does not change it). Writes the terms to AgentSLA's database; moves no funds. Returns jobId and the registered maxLatencyMs. The oracle then settles the job automatically within about 20 minutes (see get_escrow_job).

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": {
      "txHash": "<txHash>",
      "maxLatencyMs": "<maxLatencyMs>"
    },
    "name": "register_escrow_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
txHashYesHash of the confirmed createJob transaction, 0x + 64 hex characters.
maxLatencyMsYesThe SLA: the endpoint must answer 2xx/3xx within this many milliseconds, e.g. 1000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the authorization rule ("only its creator's transaction is accepted"), the persistence target ("AgentSLA's database"), the absence of fund movement, the one-way write semantics ("the first registration is kept"), and the downstream consequence ("oracle then settles the job automatically within about 20 minutes"). These are exactly the behavioral facts an agent cannot infer from readOnlyHint/destructiveHint/idempotentHint alone.

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?

Front-loaded with the action and the lifecycle trigger, and the later sentences each carry distinct facts (auth, idempotency, storage, return value, settlement window). It is dense rather than bloated, though the third sentence stacks several constraints and could be split for faster scanning.

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?

With no output schema, the description supplies the return values ("jobId and the registered maxLatencyMs") and the downstream settlement timing. Combined with the prerequisite and authorization rules, an agent has everything needed to invoke it correctly on the first try.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by tying txHash to a confirmed createJob transaction on Base that must come from the job's creator, which is a constraint the schema pattern alone cannot convey. maxLatencyMs is largely left to the schema's own SLA definition, so it is not a full 5.

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?

States a specific verb and resource ("Records the latency limit for an escrow job") and immediately bounds it in the lifecycle ("after its createJob transaction confirms"), which separates it from create_escrow_job and get_escrow_job. It also names the effect ("so the oracle knows the SLA to judge"), so the agent knows why the tool exists, not just what it writes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit timing ("once per job, right after the create_escrow_job transactions") and an explicit re-call rule ("calling again does not change it"), and points to get_escrow_job for the settlement side. An agent has enough to decide when to call this versus reading job state.

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