Skip to main content
Glama

policy_trigger_now

Trigger an immediate crawl for a specified policy while bypassing its cron schedule; open runs are skipped and oversized estimates are refused unless force is set.

Instructions

Trigger a crawl for the policy immediately.

Bypasses the cron schedule but still enforces single-flight (skips if an open run exists) and the plan-size guardrail (refuses if estimate exceeds POLICY_MAX_FETCHES unless force=true).

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": {
      "policy_id": "<policy_id>"
    },
    "name": "policy_trigger_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
policy_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing real runtime behavior: single-flight semantics (skips when an open run exists) and a plan-size guardrail tied to POLICY_MAX_FETCHES that can refuse the call. Annotations only declare it is a non-read-only, non-idempotent, non-destructive write; the description adds that the call can silently no-op or be rejected. It stops short of describing the returned run object, but an output schema exists to cover that.

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?

Two tight sentences with the action front-loaded before the caveats, and no filler wording. The only cost is the dangling 'force=true' clause, which is short but misleading rather than simply verbose.

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?

For a mutation tool with a valid output schema, the description covers the important failure modes (single-flight skip, size refusal) and needs not explain return values. The picture is incomplete because it advertises an override mechanism the schema does not support, leaving an agent unsure how (or whether) the guardrail can be bypassed.

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%, so the description must carry parameter meaning, but it never explains policy_id (the sole required parameter). Worse, the only parameter-specific claim references 'force=true', which is absent from the schema (additionalProperties: false), so an agent following the description would attempt an invalid argument.

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?

States a specific verb and resource: 'Trigger a crawl for the policy immediately,' and adds scoping detail ('bypasses the cron schedule') that separates it from scheduled triggering. It does not name a sibling (e.g., policy_estimate or policy_runs) explicitly, so 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'immediately' plus 'bypasses the cron schedule' implies when to use this over a scheduled path, which is useful context. However, there is no explicit when-not guidance or named alternative, and the suggested escape hatch 'force=true' is not a valid parameter, which would misdirect an agent trying to override the guardrail.

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