Skip to main content
Glama

AutoPay

get_job

Poll a previously queued AutoPay job by id until status is done.

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": {
      "id": "<id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavior: this is a repeated poll that ends when status is 'done.' It omits poll cadence, timeout/retry limits, non-'done' terminal states such as failure, and whether the job is retained afterwards — meaningful gaps for a polling tool.

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?

One sentence, front-loaded with the verb and resource, with no filler. It is arguably under-specified rather than verbose, but the wording itself earns its place.

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 one-parameter polling tool with no output schema and no annotations, the description should explain what status values can come back and what a completed job yields. It covers the polling loop's exit condition but leaves return shape and failure semantics undocumented.

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 description coverage is 0% — the single 'id' parameter is a bare string with no description anywhere. The description only implies the id identifies a 'previously queued AutoPay job'; it does not specify the id's format, origin, or whether it is the same id returned by the queueing tool.

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?

The description states a specific verb and resource: 'Poll a previously queued AutoPay job by id.' An agent can immediately tell this is a status-check tool for jobs created elsewhere, not a search or fetch tool. It does not name a sibling it is distinct from, keeping it just short of a 5.

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?

'previously queued' implies this is used after a job-submission tool, which gives implicit sequencing guidance. However, it never states when to stop polling, what to do on failure, or how it differs from the sibling 'fetch' tool that might also retrieve an object by id.

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