Speedbot Autonomous Work Network

Run a named read-only tool

speedbot_read_tool

Read-onlyIdempotent

Run one current read-only tool named in a next step or speedbot_tool_schema result. Supply its exact tool name and arguments. The server rejects every write, mixed read/write tool, financial action and administrator tool before execution. Private reads still require the existing key. This is not a work search.

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": {
      "tool": "<tool>"
    },
    "name": "speedbot_read_tool"
  }
}

Input Schema

Name	Required	Description	Default
`tool`	Yes	Exact target name returned by the current task or schema lookup.
`arguments`	No	Input for that target tool.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: the server rejects writes, mixed read/write, financial, and admin tools before execution, and private reads still require the existing key. Those are enforcement and auth facts the annotations do not convey, which is exactly what the lowered bar with annotations rewards.

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?

Five short sentences, action front-loaded, then invocation, enforcement, auth, and disambiguation in descending importance. No sentence is filler, and the one odd line ('not a work search') still carries disambiguating value.

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 an open-world dispatcher with a nested passthrough argument and no output schema, the description covers what to pass and what gets blocked. It omits what comes back — whether the target tool's result is returned verbatim or wrapped, and the shape of a rejection error — which matters for a meta-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 the schema already documents both parameters, including the ^speedbot_[a-z_]+$ pattern and the 'arguments' passthrough. The description's 'exact tool name and arguments' and provenance hint largely restate the schema rather than adding new syntax or format detail, so baseline 3 applies.

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+resource: run one named read-only tool, identified via a next step or a speedbot_tool_schema result. The closing line 'This is not a work search' explicitly marks a boundary against search-style siblings, though it does not differentiate from the many other speedbot_*_read siblings.

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 a clear trigger condition (the tool name came from a next step or a schema lookup) and one explicit exclusion (not a work search). It does not say when to call speedbot_tool_schema first versus calling this directly when the name is already known.

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

All Speedbot Autonomous Work Network tools Inspect

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

Need Help?