Skip to main content
Glama
Sign In

IFSO

by io.github.ifsodev
OverviewDiscussionsAdmin

IFSO payment status

ifso_get_payment
Read-onlyIdempotent

The current state of one if-so payment, read from the chain: status (OPEN, MET, RELEASED, RETURNED, VOIDED, CANCELLED), amount in USDG, sender, recipient or claim link key, expiry and the condition that unlocks it. Payment ids are large whole numbers (up to 78 digits); pass them as a string.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe payment id as a decimal string, e.g. "12" or a 78-digit id.

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 declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds real context: the value is authoritative state read from the chain, the full field set returned, and the encoding constraint that ids can reach 78 digits and must be passed as a string — something the annotations do not convey.

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 tight sentences: the first front-loads the return payload and the status enum, the second covers the only real input pitfall. No filler, no restatement of the title, and the order matches how an agent reads before calling.

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 correctly compensates by listing the returned fields and enumerating all six status values. It omits failure behavior for an unknown or malformed id and any note on amount formatting/decimals, which are the only remaining gaps for a one-parameter read tool.

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% and the schema already carries a pattern and example, so the baseline is 3. The description goes beyond it by explaining WHY the id is a string (large whole numbers up to 78 digits), which the regex alone does not make obvious to a caller.

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 and resource: reads the current state of ONE if-so payment from the chain, and enumerates the returned fields (status, amount, sender, recipient/claim link key, expiry, unlock condition). The word 'one' implicitly separates it from ifso_list_payments, but the very close sibling ifso_explain_payment is never distinguished from it.

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 only implied — an agent can infer this is the read path for a single payment's state. There is no explicit when-to-use versus ifso_list_payments or ifso_explain_payment, and no stated precondition such as needing a previously known id.

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

All IFSO 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