Skip to main content
Glama
DecisionPen MCP Server

DecisionPen MCP Server

Official
by DecisionPen

rerun_enrichment_job

Re-queue a failed or completed application enrichment job using the same sources; suggestions are replaced while map items remain. Blocked for pending, queued, or running jobs.

Instructions

Re-queue a failed or completed application_enrichment job (same sources). Blocked while pending/queued/running. Suggestions are replaced; map items stay.

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": "rerun_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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the state guard (blocked while pending/queued/running) and the destructive side effect ('suggestions are replaced; map items stay'), which tells an agent exactly what data is lost versus preserved. It omits permission/auth requirements and whether the rerun executes synchronously or returns immediately, so it stops short of full behavioral disclosure.

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, all front-loaded: action and eligibility first, blocking constraint second, mutation consequence last. Every sentence contributes new information and nothing is repeated.

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-purpose, single-parameter mutation tool with an output schema (so return values need no explanation), the description covers eligibility, blocking, and data-replacement effects adequately. The remaining gap is the job_id semantics and the lack of an explicit fallback when the job is in a blocked state.

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?

Schema description coverage is 0% and the single job_id parameter carries only a title, so the description is the only source of meaning — yet it says nothing about how to obtain the job_id, its format, or whether it must reference a job in a terminal state. Since rerun is restricted to failed/completed jobs, that constraint on the id is exactly the semantic an agent needs and it is only implied by the state guard.

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 pairs a specific verb (re-queue) with a specific resource (application_enrichment job) and narrows the scope to jobs that are failed or completed. That makes recency/state clear without naming a sibling tool explicitly, so an agent can distinguish it from get_enrichment_job or propose_enrichment, but the differentiation is inferred rather than stated.

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 gives a concrete eligibility condition ('failed or completed') and a concrete exclusion ('blocked while pending/queued/running'), which is genuine when-to-use and when-not guidance. It does not name an alternative action for the blocked case (e.g., wait or cancel), leaving the fallback path unspecified.

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