Skip to main content
Glama

policy_enable

Idempotent

Activate a crawl policy by its integer policy_id so scheduled crawls and source-fetch rules take effect. Use it to turn on a configured policy that is currently disabled.

Instructions

Enable 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_enable"
  }
}

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.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what enabling actually causes (e.g., scheduling crawls), what happens if the policy is already enabled, or whether an error or no-op results.

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 single four-word sentence is front-loaded and free of waste, but it is under-specified rather than genuinely concise. Nothing in it is unnecessary; there is simply too little of it.

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 described, and annotations cover the mutation profile. Still, for a state-changing toggle the definition omits what the state change entails and any idempotency/error behavior in prose, leaving the agent dependent on structured fields alone.

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 ideally clarify the single parameter, and it does not. However, policy_id is a required integer whose meaning is self-evident from the tool name and is consistent across the policy_* sibling family, making the practical risk low.

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 gives a specific verb and resource ("Enable a crawl policy"), so an agent knows exactly what operation is performed. It stops short of differentiating from siblings such as policy_disable or policy_update, but the core action 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 Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g., the policy must exist and be in a disabled state), and no reference to the obvious alternative policy_disable. The agent must infer the selection criteria entirely from the name.

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