Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Get a quick read

get_quick_read
Read-onlyIdempotent

Status and results so far of a quick read. Pass wait (up to 25 s): the answer returns as soon as one more agent has finished; call again while status is queued or running, relaying each new agent.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_quick_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoSeconds to wait for the next agent to finish, 0-25 (default 0)
run_idYesRun id from quick_read
includeNotext: include each agent's full write-up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds meaningful polling semantics beyond that: the call returns as soon as one more agent finishes, and the agent should call again while status is queued or running.

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?

Two sentences, both front-loaded and useful. The first states the purpose; the second explains the polling behavior without repetition or filler.

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?

Covers the key async polling behavior needed to invoke the tool correctly. With no output schema, it could still say more about terminal statuses or the exact shape of returned status/result fields, but it is mostly complete for a polling retrieval 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%, so `run_id`, `wait`, and `include` are already documented in the input schema. The description adds a small amount of meaning to `wait` by explaining that the answer arrives as soon as another agent finishes, but it does not add semantics for `include` or `run_id` beyond the schema.

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: retrieving the status and results so far of a quick read. It implies the distinction from the sibling `quick_read` by focusing on ongoing status/results, but does not explicitly name the sibling or contrast the two.

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?

Gives clear operational guidance: pass `wait` to block up to 25 seconds, call again while status is queued or running, and relay each new agent as it completes. It does not explicitly say when to use `quick_read` instead or when to stop polling, but the polling loop is well specified.

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

All SimianX AI 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