Skip to main content
Glama

Ego Agent Marketplace

Get one paid API

get_service
Read-onlyIdempotent

Everything needed to call one paid API found with search_services: its url, price, the wallet it is paid to, its input and how to pay over x402. Free, read-only; it does not call or pay the API.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe id from search_services.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description's useful addition is that access is 'Free' and that reading metadata does not trigger payment or the API call itself, which annotations cannot express. Return contents are listed, but nothing is said about failure behavior for a missing/invalid id.

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 dense sentences with zero filler; the returned-fields enumeration is front-loaded and the scoping disclaimer is placed last where it reads as a caveat. Every clause carries information.

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 one-parameter read tool with no output schema, the description compensates well by enumerating the returned fields and stating the no-payment behavior. It is not fully complete in that error/empty-result behavior for an unknown id is unaddressed, but nothing needed for a correct call is missing.

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?

With 100% schema description coverage and a single required 'id' already documented as 'The id from search_services', the schema carries the parameter semantics. The description reinforces provenance of the id but adds no format, length, or validation detail beyond what the schema pattern and description already supply, so 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?

The description names a specific verb and resource ('get one paid API') and enumerates exactly what comes back: url, price, payee wallet, input shape, and payment method over x402. It also anchors the tool to the sibling that produces its input ('found with search_services'), so an agent can distinguish it from search_services and trade_check without opening a schema.

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?

Usage context is clear: it is the follow-up call after search_services, and it explicitly draws the boundary that it 'does not call or pay the API', preventing an agent from assuming retrieval equals invocation. It stops short of stating error conditions (e.g., unknown id) or contrasting with trade_check, so no explicit when-not guidance beyond the payment disclaimer.

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