Skip to main content
Glama
DecisionPen MCP Server

DecisionPen MCP Server

Official
by DecisionPen

get_enrichment_job

Polls the status of a DecisionPen enrichment job and confirms when it is review-ready. Use it to check whether processing has completed and a preview is available.

Instructions

Poll DecisionPen enrichment job status. Review-ready when status=completed and a preview is present. Same auth caps as propose_enrichment.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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. It usefully discloses the state semantics that define a finished, reviewable job (status=completed plus a preview) and that authorization mirrors propose_enrichment, but says nothing about polling cadence, whether jobs expire, or what happens for an unknown or unauthorized job_id.

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 sentences with no filler: purpose first, then the completion condition, then the auth note. The auth sentence is slightly cryptic on its own, but overall nothing is wasted.

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?

The tool is simple (one required parameter) and has an output schema, so return values need no explanation. Still, for a polling tool the description leaves gaps around job_id provenance, polling behavior, and failure modes, which are exactly the things an agent must know to invoke it correctly.

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 0%, so the description would need to explain job_id's origin or format, and it does not do so explicitly. The only indirect help is the reference to propose_enrichment, which hints at where a job id comes from; the parameter itself is otherwise undocumented beyond its self-evident name.

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?

"Poll DecisionPen enrichment job status" gives a specific verb and resource, so the agent knows this is a status-check for an enrichment job rather than a mutation or a rerun. It does not explicitly contrast with rerun_enrichment_job, so it falls short of the top score, but the purpose is unambiguous.

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 implied through the word "Poll" and the tie to propose_enrichment ("Same auth caps as propose_enrichment"), suggesting this is called after a job is proposed. The completion criterion ("review-ready when status=completed and a preview is present") is genuinely useful guidance, but no alternative (e.g., rerun_enrichment_job) or termination condition for polling is named.

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