Skip to main content
Glama

Portfolio job status and results

get_portfolio_job
Read-onlyIdempotent

The status of a portfolio job (queued, running, done, failed, expired) and, once done, the per-site results and summary. Polling is free. Results are deleted after the job's expires_at.

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_portfolio_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: the job lifecycle states, that polling has no cost, and that results expire and are deleted, which tells the agent to retrieve results before expires_at.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no wasted wording. The status purpose is front-loaded, followed by the result availability and the expiry constraint.

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 single-parameter read-only status tool with annotations and an output schema, the description is largely complete: it covers lifecycle states, polling behavior, and result expiry. The main omission is any indication of where the required job_id comes from.

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?

There is one parameter (job_id) with 0% schema description coverage, so the description carries the burden of explaining it. It never says what a job_id is, where to obtain one, or how it relates to estimate_portfolio; only the schema pattern constrains the value.

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 resource ("portfolio job") and what is returned ("status... and, once done, the per-site results and summary"), and it enumerates the possible statuses. It does not explicitly distinguish this tool from siblings such as estimate_portfolio, which keeps it from 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?

"Polling is free" and "results are deleted after the job's expires_at" imply repeated status checks and a deadline for fetching results, which is useful usage context. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative.

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