Skip to main content
Glama

register_loop

Register an open loop (refund, return, price_adjustment, delivery, unanswered, other). Returns TRACE receipt. Needs an API key: keyless calls are read-only (get_loop, list_due).

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": {
      "kind": "<kind>",
      "counterparty": "<counterparty>",
      "due_at": "<due_at>"
    },
    "name": "register_loop"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
notesNo
due_atYesISO-8601 datetime with offset
currencyNo
source_urlNo
amount_centsNo
counterpartyYes
external_refNo
deadline_desk_receipt_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it discloses the auth requirement and that a TRACE receipt is returned, which are genuinely useful. It omits duplicate/idempotency behavior (e.g., external_ref), error modes, and whether re-registering the same loop overwrites or rejects — material gaps for a write tool.

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 short sentences, zero filler; the operation and its kinds are front-loaded and the auth caveat follows immediately.

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

Completeness2/5

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

A nine-parameter write tool with no annotations, no output schema, and near-zero schema documentation needs far more from the description than an auth note and receipt mention. An agent cannot infer the semantics of most fields or the failure behavior from this text.

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

Parameters2/5

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

Schema description coverage is only 11% (just one of nine params documented), so the description must compensate and does not: counterparty, notes, currency, source_url, amount_cents, external_ref, and deadline_desk_receipt_id are all unexplained. The kind list it repeats is already fully enumerated in the schema.

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?

States a specific verb+resource ('Register an open loop') and enumerates the domain kinds inline, so the agent knows exactly what is being created. Sibling names (get_loop, list_due) appear only as keyless read alternatives rather than as explicit contrast for this operation.

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?

Gives a concrete precondition ('Needs an API key') and states the fallback behavior when unauthenticated (keyless calls are read-only: get_loop, list_due), which effectively routes the agent. It stops short of saying when to choose this over the read tools in an authenticated context, but the usage condition is clear.

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