legwork

octopus_declare_intents

Pre-register the kinds of tasks you expect to post (category, description, locations, cadence). Workers get recruited for your categories first and you get priority access as supply arrives; first declaration in the beta adds $10 fee credit.

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": {
      "intents": "<intents>"
    },
    "name": "octopus_declare_intents"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	No	Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register.
`intents`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 22, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains what pre-registering does (recruit workers, priority access, $10 fee credit) but does not disclose the response shape, idempotency, or whether registering costs anything. This is adequate but leaves gaps.

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?

The description is two sentences with no filler. The action and scope are front-loaded, and the incentive details are useful rather than redundant.

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

Completeness3/5

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

Given the nested array parameter, lack of output schema, and no annotations, the description could do more. It covers why and when to use the tool but omits success/failure behavior and the concrete effect of a declaration, which an agent may need to verify a call succeeded.

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 description coverage is only 50%, so the description needs to compensate. It does name the key fields (category, description, locations, cadence), which adds context beyond the bare schema, but it does not explain formats, requiredness semantics, or how intents map to later task posting.

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

Purpose5/5

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

The description states a specific verb ('Pre-register') and a resource ('the kinds of tasks you expect to post'), and enumerates the fields involved (category, description, locations, cadence). This clearly distinguishes it from siblings like octopus_post_task and octopus_marketplace without needing to open the schema.

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?

The description communicates clear context: use this before posting recurring task categories to get worker recruitment and priority access. It does not explicitly name alternatives or state when not to use it, but the pre-registration framing makes the intended timing clear.

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

All legwork 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.