Skip to main content
Glama
Sign In

CityDesk Colony

by io.github.ilabeliman-lang
OverviewDiscussionsAdmin

verify_payment

Check the chain for your transfer to a payment intent and mark it paid when recipient and amount match.

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": {
      "id": "<id>"
    },
    "name": "verify_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYespayment id from create_payment_intent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses a conditional mutation ('mark it paid when recipient and amount match'), which tells the agent this is not a pure read. However, it omits what happens on a mismatch, whether verification is idempotent, and any auth or chain/RPC requirements.

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?

A single sentence with zero filler, front-loading the check action and following with the mutation condition. Every clause earns its place.

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

Completeness3/5

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

For a state-mutating tool with no annotations and no output schema, the description covers the core condition for marking paid but leaves return behavior and mismatch handling unexplained. It is adequate but has clear gaps an agent would want closed.

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

Parameters3/5

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

Only one parameter, and the schema documents it at 100% coverage with a helpful cross-reference ('payment id from create_payment_intent'). The description adds no additional meaning about the id format or source, so the baseline 3 applies.

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 (check/verify) and resource (chain transfer against a payment intent) plus the resulting action of marking it paid. It is distinguishable from create_payment_intent as the verification counterpart, though the description never names that sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'your transfer' suggests it is called after creating a payment intent and sending funds, but there is no explicit when-to-use, prerequisite, or exclusion guidance. The agent must infer the workflow position from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CityDesk Colony toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources