Skip to main content
Glama
Sign In

Primavera

by com.primaverapp
OverviewDiscussionsAdmin

Progress of a job

get_job
Read-onlyIdempotent

Progress of a job: status, places done and billed, credits spent; for a finished filter or question job, the places per verdict.

Free.

Same call as GET /api/v1/jobs/{id} of the REST API.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYesId of a job (from start_list_job or get_list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description's main added value is the cost disclosure ('Free.') and the conditional shape of the result for finished jobs. Both are genuinely useful facts an agent cannot get from the annotations or schema. It does not cover polling cadence or whether results persist after completion.

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 short, front-loaded fragments: what is returned, the cost, and the REST equivalent. Nothing is padded, and the most important content (the returned fields) leads. The sentence structure is slightly fragmentary but efficient.

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?

With no output schema, the description must carry return-value information, and it does list the main result fields and the special verdict breakdown. For a one-parameter read tool with full annotation coverage, this is close to complete; only polling/expiry behavior is left unstated.

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?

There is a single required parameter with 100% schema description coverage, and the schema already explains that jobId comes from start_list_job or get_list. The description adds no further meaning about the id, so the baseline of 3 applies.

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 names a specific resource (a job) and enumerates what is returned: status, places done and billed, credits spent, plus per-verdict places for finished filter/question jobs. That is far more informative than the title alone and clearly marks this as the read-side counterpart to start_list_job / estimate_list_job. It stops short of explicitly naming those siblings, so it is not a full 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?

Usage is only implied: an agent must infer that this is the tool to poll after starting a job. The description never says when to call it, whether it should be polled repeatedly, or how it differs from estimate_list_job. The conditional clause about finished filter/question jobs is the only situational guidance offered.

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

All Primavera 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