Skip to main content
Glama

Safe-Send Check: crypto support triage, sanctions and scam screening

Claim the credits key after your transfer (free)

credits_claim
Read-onlyIdempotent

FREE. After the transfer from credits_quote has landed on Base, returns your ssk_ credits key (claiming again returns the same key). Then set the MCP header "Authorization: Bearer " or pass _meta["safe-send/credits-key"].

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": {
      "quote": "<quote>"
    },
    "name": "credits_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteYesThe quote id from credits_quote (q_ + 22 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the result is a secret credential and explains exactly how to consume it (Authorization: Bearer header or _meta["safe-send/credits-key"]). It also gives concrete idempotency behavior ('claiming again returns the same key'), which grounds the idempotentHint annotation in observable behavior.

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, with cost ('FREE') and the triggering condition front-loaded before the payoff and the usage instruction. Nothing redundant.

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 correctly fills that gap by describing the returned key and how to send it. Prerequisite, idempotency, and post-call action are all covered for a one-parameter tool.

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?

Schema coverage is 100% and the quote parameter is already documented in the schema, including the q_ + 22 character format. The description adds only that the id originates from credits_quote, so the baseline 3 applies.

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 ('returns your ssk_ credits key') plus the exact precondition ('after the transfer from credits_quote has landed on Base'), which cleanly separates it from the sibling credits_quote that produces the transfer.

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?

Names the prerequisite tool (credits_quote) and the required state (transfer landed on Base), which effectively tells an agent when to call it. It does not spell out failure/exclusion cases such as calling before the transfer confirms, so it stops short of a full when/when-not treatment.

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