Skip to main content
Glama

policy_delete

Destructive

Deletes a crawl policy and all associated runs via cascade, preventing orphaned run records when retiring a policy.

Instructions

Delete a crawl policy and all its runs (cascade).

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

Input Schema

NameRequiredDescriptionDefault
policy_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds real beyond-annotation context by disclosing cascade behavior — that all associated runs are removed too — which is exactly the kind of collateral damage an agent must know before invoking it. It does not mention irreversibility or behavior when the policy is absent, keeping it short of a 5.

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?

A single sentence that front-loads the verb, resource and cascade scope with no filler or redundancy.

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?

With annotations covering destructiveness/non-idempotency, an output schema present, and only one simple parameter, the description covers what an agent needs to select and call the tool. A note on error behavior for a missing policy or irreversibility would make it fully complete.

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?

There is one parameter, policy_id, with 0% schema description coverage, so the description would need to compensate and it does not. The parameter is nonetheless unambiguous from the tool name and the integer type, so an agent will not misread it, but no added meaning (e.g., whether it accepts only IDs, not names) is provided.

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 names a specific verb and resource ('Delete a crawl policy') and adds scope ('and all its runs'), which lets an agent distinguish it from sibling policy_disable/policy_enable at a glance. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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?

Usage is only implied by the destructive verb; the description never states when to delete rather than disable, nor any prerequisite or confirmation step. An agent can reasonably infer intent, but no explicit alternative routing is supplied.

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