Skip to main content
Glama

Describe the job, get it done: one call over the whole toolbox

do

Use when an agent has a job to get done and does not know which tool or in what order: describe it in plain words and it happens in ONE paid call: picks from 71 capabilities - transcription, translation, documents, images, web, on-chain, domains, IPs, weather, FX - fills their parameters and chains up to 3 steps, feeding each result into the next. Priced per job: the 402 challenge quotes YOUR job before you sign, from $0.02. If nothing fits, nothing is charged. $0.02 per call, paid over x402 (USDC).

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": {
      "job": "<job>"
    },
    "name": "do"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesThe job to do, in plain words. Example: read this page and translate it to Spanish.
inputNoOptional data the job needs: a URL, an EVM address, a domain, or text.
auto_planNoOptional POST-only automatic planner, mutually exclusive with explicit plans. Fixed charge $0.015 + tool_budget_usdc, at most $0.15 total, with no rebate for unused budget. External delegation additionally requires allow_external:true, external_budget_usdc up to $0.05, external_tools curated IDs and current curation_version from /v1/do/market. Both operator activation and a typed approved catalogue are required. A job's text cannot authorize external calls.
max_stepsNoHow many tools may be chained, 1 to 3. Default 2.
plan_stepsNoOptional POST-only explicit mixed plan: 1-3 total steps, each {route, params} for a local catalogue tool or {url, params} for an eligible verified market entry. Use exact top-level $previous after the first step to pass text. A plan containing an external URL requires enabled isolated purchasing; local-only plans do not.
market_stepsNoOptional POST-only explicit external plan: 1-3 objects with url and params from a verified catalogue entry. Requires enabled isolated purchasing wallet; no example data is reused. Current execution supports GET entries and explicitly curated POST entries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / auto_plan
      Added value: +{
      +  "description": "Optional POST-only automatic planner, mutually exclusive with explicit plans. Fixed charge $0.015 + tool_budget_usdc, at most $0.15 total, with no rebate for unused budget. External delegation additionally requires allow_external:true, external_budget_usdc up to $0.05, external_tools curated IDs and current curation_version from /v1/do/market. Both operator activation and a typed approved catalogue are required. A job's text cannot authorize external calls.",
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / plan_steps
      Added value: +{
      +  "description": "Optional POST-only explicit mixed plan: 1-3 total steps, each {route, params} for a local catalogue tool or {url, params} for an eligible verified market entry. Use exact top-level $previous after the first step to pass text. A plan containing an external URL requires enabled isolated purchasing; local-only plans do not.",
      +  "type": "array"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / market_steps
      Added value: +{
      +  "description": "Optional POST-only explicit external plan: 1-3 objects with url and params from a verified catalogue entry. Requires enabled isolated purchasing wallet; no example data is reused. Current execution supports GET entries and explicitly curated POST entries.",
      +  "type": "array"
      +}
  4. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the paid nature, that a 402 challenge quotes the specific job before signing, the $0.02 base price, that a no-match job is free, and that chaining is capped at 3 steps. It omits return shape, latency, and failure/partial-failure behavior, which keeps it from a 5.

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

Conciseness4/5

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

Single dense paragraph, front-loaded with the usage trigger and capability scope before pricing. Minor waste in restating price twice ("from $0.02" and "$0.02 per call, paid over x402"), but otherwise every clause carries information.

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?

A 6-parameter tool with nested objects, no annotations and no output schema needs the description to say what comes back, and it never does. Cost, payment rail and chaining limits are covered, but an agent cannot tell what the response payload looks like or how partial step failures are reported.

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 100%, so the schema already documents job, input, auto_plan, max_steps, plan_steps and market_steps in depth. The description reinforces chaining semantics (up to 3 steps, each result fed into the next) but adds no syntax or constraint detail beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific action (describe a job in plain words, it executes in one call) over a well-scoped resource (71 capabilities across transcription, documents, web, on-chain, etc.), and explicitly positions itself as the orchestrator distinct from the atomic siblings. An agent can tell immediately this is the meta/dispatcher tool rather than any single capability.

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?

"Use when an agent has a job to get done and does not know which tool or in what order" gives a clear triggering condition and implicitly excludes the case where the agent already knows the target tool. It does not explicitly say "use sibling X instead when you know the tool", so it stops short of naming alternatives, but the context is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources