Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

get

Read-only

Get full details + ready-to-paste call template for a service.

Returns the service card with payment, call, quality, resource samples,
and ready-to-use MCP/x402 call hints. Use this after `search` or
`ask_services` before paying/calling an external service.

Args:
    slug: Service slug as returned by `search` items.

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": {
      "slug": "<slug>"
    },
    "name": "get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesService slug as returned by `search` items.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Service slug as returned by `search` items."
  2. 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=true and openWorldHint=false, so the bar is lower, and the description usefully adds that the result includes ready-to-paste call templates and hints. It doesn't disclose whether fetching is metered or whether the card reflects cached versus live data.

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 core purpose and usage sequencing are front-loaded in two tight sentences. The trailing Args block duplicates the input schema and is the only dead weight.

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 and full param coverage, the description needn't explain return values, and it covers purpose and sequencing adequately. Nothing critical is missing for a single-param read 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 sole `slug` param is already documented as coming from `search` items. The description's Args block restates the schema verbatim, adding no new format or constraint details, so baseline 3 applies.

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 ("Get full details ... for a service") and enumerates the returned contents (payment, call, quality, resource samples, MCP/x402 hints). It doesn't distinguish itself from siblings like get_mcp_server or get_paid_verification, but the "service" resource is clearly scoped.

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?

"Use this after search or ask_services before paying/calling an external service" gives explicit sequencing and names the prerequisite alternatives. No when-not guidance or explicit exclusion of other get_* siblings, so it stops short of a 5.

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.