Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

jobs_id

Retrieve or poll an asynchronous Fetchproof job by ID to check its status and collect the finished result; use the ID returned in the 202 response.

Instructions

jobs: Get or poll a job. GET /v1/jobs/{id}. Poll a job created by adding async=true, or the header Prefer: respond-async, to any GET /v1 request. A queued job has not been charged. A finished job's result is the operation body, charged once through the normal ledger. Failed, empty, expired and cancelled jobs cost 0. Costs 0 credits when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
idYesJob id from the 202 response. Pass that id and nothing else.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so extensively: it discloses queued, finished, failed, empty, expired, cancelled, error, blocked, timed-out, invalid, cache-hit, not-found, and empty-result billing semantics. An agent knows what costs credits and what does not before calling.

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?

The definition is front-loaded with purpose and usage before moving into billing details. It is somewhat long, but each sentence adds a distinct cost or job-state behavior rather than repeating structured fields.

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

Completeness4/5

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

For a one-parameter GET/poll tool with no output schema, the description covers the async creation path, job states, result body semantics, and credit charging thoroughly. It does not specify polling cadence or status field values, but the essential context an agent needs to call it is present.

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 coverage is 100%, and the schema already says the id comes from the 202 response and must be passed alone. The description adds no parameter-level meaning beyond the path placeholder, so the baseline 3 is appropriate.

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?

The description opens with a specific verb and resource: 'Get or poll a job. GET /v1/jobs/{id}.' This clearly distinguishes it from the sibling cancellation tool jobs_id_cancel_post and gives an agent enough to identify the operation without opening the schema.

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?

It explains the trigger condition precisely: poll a job created by adding async=true or the Prefer: respond-async header to any GET /v1 request. It does not explicitly name exclusions such as when to use the cancel sibling, but the async-job context is clear.

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

Deploy Server

Other Tools