Skip to main content
Glama

policy_update

Idempotent

Update an existing crawl policy by changing only the fields you specify, leaving all other settings unchanged.

Instructions

Update a crawl policy. Only provided fields are changed.

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

Input Schema

NameRequiredDescriptionDefault
modeNo
nameNo
forceNo
scriptNo
enabledNo
executorNo
timezoneNo
cron_exprNo
frequencyNo
policy_idYes
entity_idsNo
concept_idsNo
date_policyNo
entity_typeNo
script_argsNo
source_filterNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare mutation (readOnlyHint=false), idempotency, and non-destructiveness, so the bar is lower. The description adds the useful PATCH-style semantics that omitted fields are untouched, but says nothing about what `force` does, validation failures, or side effects on runs/schedules.

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 short sentences, front-loaded with the action and immediately followed by the key semantic. Efficient, though bordering on under-specification for a 16-parameter mutation tool.

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?

With 16 undocumented parameters, no annotations explaining required-permission implications, and no parameter-level detail anywhere, this description is too thin for the tool's complexity. The existence of an output schema excuses return-value explanation, but not the parameter and behavior gaps.

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% across 16 parameters, so the description must carry parameter meaning and it explains none of them. The single implicit hint is that null/unprovided fields mean 'unchanged', but it never names any parameter or clarifies cron_expr vs frequency, mode, executor, or script_args.

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 ('Update a crawl policy') and adds the partial-update scope ('only provided fields are changed'), which distinguishes it from a full-replace operation. It does not, however, distinguish itself from siblings such as policy_enable, policy_disable, or policy_create.

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?

No when-to-use guidance at all: nothing says when to prefer this over policy_enable/policy_disable for toggling `enabled`, or over scope_update/update_binding for related resources. The partial-update note is a mechanic, not usage guidance.

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