Skip to main content
Glama

agent-exec service card

service_card
Read-only

FREE: what agent-exec sells, each price, and how to pay (x402, USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer, no account). Moves no money. Feedback: POST /feedback (free). Read daily; no individual reply.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
quoteYes
executeYes
llmsTxtYes
networkYes
openapiYes
paymentYes
serviceYes
feedbackYes
directoryYes
resourcesYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / properties / feedback
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / payment / properties / rule
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / payment / required
      Previous value: -[
      -  "protocol",
      -  "transport",
      -  "manifest",
      -  "howToPay",
      -  "identity"
      -]New value: +[
      +  "protocol",
      +  "transport",
      +  "manifest",
      +  "howToPay",
      +  "rule",
      +  "identity"
      +]
    • addedOutput schema / properties / resources / items / properties / price
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / resources / items / required
      Previous value: -[
      -  "resource",
      -  "method",
      -  "free",
      -  "description"
      -]New value: +[
      +  "resource",
      +  "method",
      +  "free",
      +  "price",
      +  "description"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "service",
      -  "description",
      -  "network",
      -  "execute",
      -  "quote",
      -  "directory",
      -  "resources",
      -  "payment",
      -  "openapi",
      -  "llmsTxt"
      -]New value: +[
      +  "service",
      +  "description",
      +  "network",
      +  "execute",
      +  "quote",
      +  "directory",
      +  "resources",
      +  "payment",
      +  "openapi",
      +  "llmsTxt",
      +  "feedback"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/destructiveHint=false annotations, the description adds real behavioral context: no money moves, no account is required, content refreshes at most daily, and feedback gets no individual reply. That last point usefully sets expectations about side-channel communication that annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loads the key facts (FREE, what it sells, how to pay). The telegraphic parenthetical list of chains and the trailing feedback/reply caveat are dense but each clause carries distinct information; only the feedback line feels slightly tangential.

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 an output schema present, the description need not explain return shapes, and it covers the essentials an agent needs: cost (free), payment rails offered, account requirement, and refresh cadence. It stops just short of explaining what a caller should do with the pricing data, but that is a minor gap for a static info 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?

The tool takes zero parameters and the description correctly introduces none, so there is nothing to mis-specify. Baseline 4 applies for a no-parameter tool.

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 states concretely what the card returns: the catalog of what agent-exec sells, each price, and accepted payment rails (x402, USDC across seven chains). 'Moves no money' implicitly separates it from transactional siblings like pay_send or relay_usdc, though no sibling is named directly.

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?

It gives 'Read daily', 'FREE', and 'no account', which imply this is a zero-cost discovery call an agent should make before paying. However, it never explicitly states when to call this versus a payment or listing tool, so the usage guidance is implied rather than spelled out.

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