Skip to main content
Glama

policy_runs

Read-onlyIdempotent

List crawl policy execution runs and filter by policy ID or status (running, success, failed) to monitor pipeline outcomes and troubleshoot failures.

Instructions

List policy runs. Optional filters: policy_id, status (running/success/failed).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "policy_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo
policy_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds the valid status states (running/success/failed), which is useful behavioral context, but says nothing about pagination, default limit of 50, or ordering of results.

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?

Two short, front-loaded sentences with zero filler: the action first, then the optional filters. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be explained, and the tool is simple with three optional parameters. However, the undocumented limit parameter and the absence of guidance relative to platform_runs/policy_list leave notable gaps for correct invocation.

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 must carry parameter meaning. It documents policy_id and enriches status with concrete values that the schema lacks (the schema only types it as string/null), but it leaves the third parameter, limit, entirely unexplained.

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+resource ("List policy runs") and names its filter scope, so the agent knows exactly what is returned. It does not distinguish itself from the nearby sibling platform_runs, which an agent could easily confuse with this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The word "Optional filters" implies when the parameters are used but gives no guidance on when to choose this tool over platform_runs or the other policy_* siblings. No exclusions, prerequisites, or context for narrowing by policy_id vs status are given.

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