Skip to main content
Glama
Sign In

Patchwell

by io.patchwell
OverviewDiscussionsAdmin

get_job_result

Read-onlyIdempotent

Fetch the result of a long transcribe or research call that returned {"status": "running", "job_id"}. Call it again every 20 to 30 seconds until status is 'done'; the finished result has the same shape as the original tool's. Patchwell settles the call's charge when the job finishes, whether you fetch it or not; a failed job costs nothing. This tool is free.

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_id": "<job_id>"
    },
    "name": "get_job_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id from a transcribe or research call that returned status 'running'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / job_id / description
      Previous value: -"The job_id from a transcribe, research or clean_data call that returned status 'running'."New value: +"The job_id from a transcribe or research call that returned status 'running'."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), and the description adds billing semantics the schema cannot express: the charge settles when the job finishes whether or not you fetch it, failed jobs cost nothing, and this call itself is free. It also tells the agent the return shape matches the original tool's, which removes ambiguity about what a 'done' response looks like.

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?

Three front-loaded sentences, each carrying a distinct fact (what it fetches, poll cadence, billing). Minor deduction for the inline {"status": "running", "job_id"} snippet, which is malformed JSON and slightly redundant with the schema's own wording.

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?

There is no output schema, and the description compensates by stating the finished result has the same shape as the originating tool's response. Combined with the polling termination condition and billing behavior, an agent has everything needed to call this correctly and to know when to stop.

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% and the parameter's own description ("The job_id from a transcribe or research call that returned status 'running'") is essentially identical to the wording in the tool description, so no meaning is added beyond the schema. 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 verb and resource ("Fetch the result of a long transcribe or research call") and pins the exact precondition: the call returned {"status": "running", "job_id"}. It also implicitly distinguishes itself from the sibling producer tools transcribe and research by naming them as the origin of the job.

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?

Gives explicit operational guidance: call again every 20 to 30 seconds until status is 'done'. That is a concrete when-to-call and when-to-stop rule, which is exactly what an agent needs for a polling tool and is rarely spelled out this well.

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

All Patchwell toolsInspect
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.

Resources