Skip to main content
Glama

policy_disable

Idempotent

Disable a crawl policy by policy_id to stop its scheduled crawling and prevent it from running until re-enabled.

Instructions

Disable a crawl policy.

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

Input Schema

NameRequiredDescriptionDefault
policy_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is partly covered. The description adds nothing beyond that: it does not say whether in-flight crawls stop, whether the policy can be re-enabled with policy_enable, or how disabling differs from deletion. For a mutation tool this leaves a real behavioral gap.

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

Conciseness3/5

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

The definition is front-loaded and free of padding, but its brevity reflects under-specification rather than economy. Every word earns its place only because there are just four of them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but the description fails to cover the state transition the tool performs or the meaning of its one required parameter. Relative to a mutation tool in a family of policy lifecycle operations, this is too thin.

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 parameter policy_id is an untyped-meaning integer with no explanation in either the schema or the description. The description does not clarify where policy_id comes from (e.g., policy_list or policy_get), leaving the only parameter semantically bare.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence gives a specific verb ('Disable') and resource ('crawl policy'), so the operation is identifiable. However, it does not distinguish this from the closely named siblings policy_enable or policy_delete, which an agent must choose between; the description is essentially a restatement of the tool name.

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?

There is no guidance on when to disable a policy versus deleting it (policy_delete) or re-enabling it, and no statement of prerequisites or state conditions. The agent must infer all usage context from the tool name alone.

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