Skip to main content
Glama

Physical Capability Cloud

operator_poll_jobs

Read-only

Operator polls jobs assigned to their kernel; status defaults to queued, and the route can filter any status. Requires operate authority for this kernel: its recorded operator identity (the caller that registered it), its proven operator wallet, or the gateway admin authority. Another identity gets 403; no credentials gets 401; an unregistered kernel gets 404 for a non-admin. Operator identity proof for operate is completed by WP-A (DECISIONS items 136 and 138). The pcc-node daemon does not call it: it takes no jobs.

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": {
      "kernelId": "<kernelId>"
    },
    "name": "operator_poll_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
kernelIdYesKernel ID to poll jobs for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Goes well beyond the readOnly/destructive annotations: it discloses the three acceptable authority sources (recorded operator identity, proven operator wallet, gateway admin) and the failure codes (403 for another identity, 401 for no credentials, 404 for an unregistered kernel non-admin). The internal references to 'WP-A (DECISIONS items 136 and 138)' add noise rather than agent-usable behavior.

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 purpose is front-loaded in the first clause, which is good, but the paragraph then mixes authorization detail with internal project bookkeeping ('WP-A', 'DECISIONS items 136 and 138') and a daemon note that a caller cannot act on. Several sentences do not earn their place for an agent deciding how to call the tool.

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?

For a single-parameter read tool with no output schema, the definition covers authorization and error outcomes well, but it omits return shape/pagination and contains the unsupported status-filter claim. The authorization material is complete enough that an agent knows the preconditions, but the response side is unaddressed.

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

Parameters2/5

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

Schema coverage is 100% and kernelId is documented in the schema, so baseline would be 3. However, the description asserts a 'status' filter that 'can filter any status' even though the input schema exposes only kernelId, which actively misleads an agent about available filtering.

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 and resource: 'Operator polls jobs assigned to their kernel', and adds the default status scope ('status defaults to queued'). It is clear what the tool does, though it never names a sibling such as get_kernel_jobs or list_jobs to differentiate itself explicitly.

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

Usage Guidelines3/5

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

Usage context is implied (an operator polling their own kernel's jobs) and the authority prerequisites are spelled out, but there is no explicit statement of when to choose this over get_kernel_jobs/list_jobs or when not to use it. The 'pcc-node daemon does not call it' note is a narrow exclusion, not general guidance.

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.