Skip to main content
Glama

execute_payment

Create AND execute a stablecoin payment on-chain in one step. Requires authentication. Uses server-side executor key to sign and broadcast the transaction.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "execute_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does add real behavior: authentication is required and signing/broadcasting happens server-side with an executor key, so the agent knows it does not need to sign anything. It omits the consequential traits for an on-chain mutation — irreversibility, failure/retry semantics, fees, and what the response contains.

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?

Three short sentences, front-loaded with the action and scope, then the auth requirement and the signing mechanism. Nothing is padded and no sentence restates the tool name.

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?

For a zero-parameter tool with no output schema and no annotations, the description covers the essential operational facts: auth needed, server-side key signs and broadcasts, single-step semantics. The main missing piece is the implicit source of payment details and the irreversibility of an on-chain broadcast, which keeps it from being complete.

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?

Zero parameters sets the baseline at 4, but this is a payment-execution tool with an empty schema, which means amount, asset, and recipient must come from somewhere implicit (session state or a prior create_payment call). The description never explains that implicit input source, so the agent cannot tell what it is actually paying or how much — a genuine semantic gap that pulls the score below baseline.

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?

The description uses a specific verb pair and resource: 'Create AND execute a stablecoin payment on-chain in one step.' The 'in one step' phrasing implicitly distinguishes it from the sibling create_payment (create-only), so an agent can infer the difference without reading another schema, though the contrast is never stated outright.

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 by 'in one step' — the agent must infer that this is the tool to pick when it wants creation plus broadcast rather than a two-step create-then-execute flow. There is no explicit when-to-use, when-not-to-use, or named alternative, and no mention of prerequisites such as a prior quote or payment record.

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