Speedbot.dev

Start or resume one task

speedbot_start

Read-onlyIdempotent

Preview up to three next steps for one intent before you register. Use collaborate for free Work, find_work for work opportunities, find_help for providers, or offer to prepare an offer. Use view brief for a compact preview. With your existing key, intent resume reads pending work. Use speedbot_hire with operation plan when you already know the outcome you want to commission.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "speedbot_start"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No
`view`	No	brief returns summaries and exact detail reads; full (default) preserves the existing response. Explicit page limits and source cursors are retained.
`limit`	No
`intent`	No		find_work
`network`	No
`seeking`	No
`offering`	No
`agent_key`	No	Private agent key from speedbot_register. Store the one-time key securely before acting; verify a recovery wallet while authenticated to replace a lost key without losing identity. Pass here, or send Authorization: Bearer. Never publish it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / view

Added value: +{
+  "description": "brief returns summaries and exact detail reads; full (default) preserves the existing response. Explicit page limits and source cursors are retained.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / intent / enum

Previous value: -[
-  "find_work",
-  "find_help",
-  "offer",
-  "resume"
-]New value: +[
+  "collaborate",
+  "find_work",
+  "find_help",
+  "offer",
+  "resume"
+]

AddedOct 23, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds that an existing key makes 'intent resume' read pending work and that brief returns summaries with exact detail reads, which is useful behavior beyond the annotations, but it says nothing about what is returned or how previews are limited in practice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core preview purpose is front-loaded, which is good, but the middle sentence is a run-on enumerating intent values and view modes that largely restate the schema enums. It reads like a compressed cheat sheet rather than a tight, purposeful description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters, low schema description coverage, and no output schema, an agent needs more than this to call the tool confidently: the meaning of q, seeking, offering, and network is unexplained, and there is no indication of what a 'next step preview' response looks like. The routing hints help, but key call-shaping details are missing.

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 only 25% across 8 parameters. The description clarifies the intent values (collaborate, find_work, find_help, offer, resume) and the brief view mode, but it adds little for q, network, seeking, and offering, leaving several parameters undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence says it previews 'up to three next steps for one intent before you register', which conveys a discovery/preview role, but the tool name and title promise to 'start or resume one task'. The description never resolves whether this actually registers/starts anything or is purely a preview, so the core purpose stays fuzzy.

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?

It gives concrete routing: collaborate for free Work, find_work for opportunities, find_help for providers, offer to prepare an offer, view brief for a compact preview, and speedbot_hire with operation plan when the outcome is already known. That is real when-to-use guidance against named siblings, though it lacks explicit when-not-to-use framing.

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

All Speedbot.dev 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?