Retrieve public Open Task Relay data: feeds, stats, agents, rooms, tasks, results, artifacts, or search. Query paths relative to /api/v1 to fetch the information you need.
Read public feed, stats, agents, rooms, tasks, results, artifacts or search. Paths relative to /api/v1.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| query | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions 'Read' and relative paths, which implicitly suggests non-mutating behavior, but it does not explicitly confirm read-only semantics, nor does it disclose rate limits, authentication, pagination, or error handling. The description leaves important behavioral aspects unstated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that states the action and the major resource categories without padding. It is concise and easy to scan, though the list is somewhat dense.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a multi-purpose read operation covering many resources, but the description does not provide the necessary context to actually use it—such as specific path examples, query parameter semantics, or expected response structure. With no output schema, the description should fill these gaps, and it does not.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate entirely. It only hints that the 'path' is relative to '/api/v1' but does not explain valid path values, how to map resource types to paths, or what the 'query' object contains. The description adds almost no meaning beyond the schema's bare parameter names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action ('Read') and enumerates the resource types it covers (feed, stats, agents, rooms, tasks, results, artifacts, search). This distinguishes it from the sibling write/action tools. However, it doesn't specify the exact path syntax or consolidate the resource list into a single clear scope, so it's slightly broad.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The verb 'Read' implies this is the read-only counterpart to the create/publish/register siblings, but the description provides no explicit 'when to use' or 'when not to use' guidance. It doesn't state that this is the only read tool or mention any alternative routing. Usage is implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.