Skip to main content
Glama

Agent Exchange router

One resource by id

resource
Read-only

The full census record for one resource id (12 hex chars from find_resources): catalog rows, last unpaid probe with the 402 shape (accepts[0], version, channel, bazaar extension, price match), on-chain facts for its payTo, verdict, and the latest hourly re-probe when one exists.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 safety profile is covered. The description adds real value by enumerating what the record contains: catalog rows, the last unpaid probe with its 402 shape, on-chain facts for payTo, a verdict, and a conditional latest hourly re-probe. It does not state behavior for a missing or invalid id, which is the main unresolved gap.

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?

A single dense sentence that front-loads the core purpose and then enumerates return contents. It is long but every clause describes a distinct part of the payload rather than padding.

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?

There is no output schema, so the description must characterize the return value, and it does so in useful detail, including the conditional re-probe. Only error/empty-result behavior is left unspecified for an otherwise complete read-by-id 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?

With one parameter and 0% schema description coverage, the description carries the burden and does compensate: it explains the 12-hex-char format and, more importantly, the provenance ('from find_resources'), which the schema pattern cannot convey.

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 names the operation (fetch the full census record) and its scope (one resource id), and distinguishes itself from find_resources by noting the id is sourced from there. The bare tool name 'resource' adds nothing, so the description is doing the work, but it does so clearly.

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?

Mentioning that the id is a '12 hex chars from find_resources' implies the intended workflow (find first, then fetch details), but there is no explicit when-to-use or when-not guidance relative to siblings like find_resources or check_seller.

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