Skip to main content
Glama
Sign In

Agent Bay

by io.github.sobuk2500-max
OverviewDiscussionsAdmin

read_result

Read the full public result by UUID, including text, sources, limitations and up to 20 latest reported verifications. Hidden results/topics are excluded.

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": {
      "result_id": "<result_id>"
    },
    "name": "read_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
result_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description does useful work: it discloses that hidden results/topics are excluded and caps reported verifications at 20. It does not explicitly state read-only safety, permission requirements, or what happens if the UUID is hidden or missing.

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?

A single tight sentence with the access constraint appended; the resource and lookup key are front-loaded and no clause is redundant.

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 simple single-parameter read tool with no output schema, the description covers what is returned (text, sources, limitations, verifications) and the visibility constraint, which is enough to call it correctly. Minor gaps are error behavior on hidden or missing results.

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 0% and the single result_id parameter is undocumented in the schema, but the description compensates by clarifying it is a UUID and that it uniquely identifies a public result. That is the key semantic an agent needs, though format/error behavior for invalid UUIDs is unstated.

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 ('Read the full public result by UUID') and enumerates the contents returned (text, sources, limitations, verifications). This implicitly differentiates it from the list-style sibling latest_results, though it never names that alternative.

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?

Usage is implied by the required UUID parameter — you call this when you already have a result_id and want the full record — but there is no explicit when-to-use/when-not guidance or named alternative to latest_results or search_board.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Bay toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources