Skip to main content
Glama

Get one listing's details

get_api_details
Read-onlyIdempotent

Returns one directory listing in full: its id, name, endpoint_url, category, link_type, current_sla_score, any verified USDC rank stake, and a summary of its signed check history (number of checks, pass rate, latest check with latency). Use it after discover_monitored_apis to judge a candidate, or to find the listing id that create_escrow_job needs. Free and read-only; it does not probe the endpoint (use check_endpoint for a live check). Give either id or endpointUrl.

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

Input Schema

NameRequiredDescriptionDefault
idNoListing id from discover_monitored_apis, e.g. 29002.
endpointUrlNoThe listing's exact endpoint_url, e.g. "https://api.openai.com". Used when id is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, and the description still adds real value: it states the call is free, that it does not probe the endpoint (a meaningful side-effect distinction from check_endpoint), and summarizes what the response contains. It stops short of describing failure behavior — e.g. what happens if the id is unknown or the URL is not listed — which is the remaining behavioral gap.

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 dense sentences: payload shape first, then the routing decision, then the lookup-key rule. Every clause carries information — the field enumeration, the sibling handoff, and the either/or constraint — with no filler or restatement of the title.

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 compensates by listing the returned fields and the check-history summary, and the read-only/free/no-probe traits cover the behavioral side. For a two-parameter lookup tool, an agent has everything needed to select and invoke it correctly.

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?

Schema coverage is 100%, so the baseline would be 3, but the sentence "Give either id or endpointUrl" supplies the one-of relationship that the schema cannot express (both properties are optional with additionalProperties=false, no oneOf/anyOf). That resolves genuine ambiguity about how the two lookup keys interact.

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?

Opens with a specific verb and resource ("Returns one directory listing in full") and then enumerates the returned fields — id, name, endpoint_url, category, link_type, sla score, stake, check history summary. It also distinguishes itself from the sibling check_endpoint by stating it does not probe the endpoint, so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use conditions: after discover_monitored_apis to judge a candidate, and to obtain the listing id that create_escrow_job requires. It also names the alternative for the live-check case ("use check_endpoint for a live check"), covering the main selection ambiguity.

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