Skip to main content
Glama
worker-mcp
by noosxe

List providers

list_providers
Read-onlyIdempotent

Lists the agent providers available to run workers and shows whether each is usable now; call before spawn_worker to choose the right provider.

Instructions

List the agent providers this server can run workers on, and whether each is usable now (its binary is found). Call it before spawn_worker to pick a provider. Each entry has its capabilities, such as whether every tool call can be gated. server.bootId and server.startedAt identify this server process; workers, runs and approvals do not survive a restart.

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": "list_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
serverYesWhich server process answered. If it differs from what you saw earlier, the server restarted: every worker, run and approval id you hold is gone, and work that was in progress is lost. Check the workspace before redoing anything.
sandboxYesWhether workers can be confined to their workspace. Without it a worker can read and write anything the server user can.
providersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • addedOutput schema / properties / server
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Which server process answered. If it differs from what you saw earlier, the server restarted: every worker, run and approval id you hold is gone, and work that was in progress is lost. Check the workspace before redoing anything.",
      +  "properties": {
      +    "bootId": {
      +      "description": "Random id of this server process; it changes on every start.",
      +      "type": "string"
      +    },
      +    "startedAt": {
      +      "description": "When this server process started (ISO 8601).",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "bootId",
      +    "startedAt"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "sandbox",
      -  "providers"
      -]New value: +[
      +  "server",
      +  "sandbox",
      +  "providers"
      +]
  2. Addedv0.6.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, closed-world), it discloses that usability depends on binary presence, that entries carry capabilities such as whether tool calls can be gated, and that workers, runs and approvals do not survive a restart. The restart-durability note is exactly the kind of state lifetime an agent cannot get from annotations.

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?

Three sentences, front-loaded with the purpose, then the usage directive, then the entry-shape and durability facts. There is no filler and every sentence adds a distinct, actionable detail.

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

Completeness5/5

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

An output schema already covers return structure, so the description only needs to orient the agent — and it does, explaining the meaning of usability, the capabilities field, and the server identity/durability caveat. Nothing an agent needs before calling spawn_worker is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly spends no words on parameter syntax and instead explains what the result entries contain.

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 verb and resource — 'List the agent providers this server can run workers on' — and adds the key discriminator that each entry reports whether it is usable now because its binary is found. No sibling tool competes for this resource, so an agent can identify it immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly prescribes when to call it: 'Call it before spawn_worker to pick a `provider`.' It names the downstream sibling that consumes the result and the prerequisite relationship, leaving nothing to inference.

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