Skip to main content
Glama

policy_create

Create a scheduled crawl policy that defines which concepts and entity types to fetch, with cron timing, crawl mode, and date-range rules.

Instructions

Create 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": {
      "name": "<name>",
      "concept_ids": "<concept_ids>",
      "entity_type": "<entity_type>"
    },
    "name": "policy_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoCrawl mode: series (one fetch per concept×entity) or per_date (default).per_date
nameYesUnique policy name.
forceNoOverride POLICY_MAX_FETCHES guardrail (default False).
scriptNoFor executor="direct": the script module name (e.g. "bulk_ingest_financials_aggregate"); mounted from a ConfigMap.
enabledNoEnable the policy (default True).
executorNo"scrapy" (default) runs the concept_crawl spider; "direct" runs a Python script (see `script`) as a k8s Job.scrapy
timezoneNoTimezone for cron evaluation (default UTC).UTC
cron_exprNo5-field cron expression (default daily at 06:00 UTC).0 6 * * *
frequencyNoPlan frequency hint: daily/weekly/monthly/quarterly/yearly (default daily).daily
entity_idsNoOptional list of entity IDs (NULL = all entities of the type).
concept_idsYesList of concept IDs to crawl.
date_policyNoDate range policy: {mode: since_last|trailing|explicit, days?, start?, end?}.
entity_typeYesEntity type (fund/stock/country/...).
script_argsNoFor executor="direct": CLI args passed to the script (e.g. ["--start-year","2015","--end-year","2026"]). --db-url is injected automatically from the cluster env.
source_filterNoOptional list of source names to restrict to (NULL = all ranked sources).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent creation operation, so the safety profile is covered. Beyond that the description adds nothing: it does not explain that creation schedules recurring crawls via cron, that it is asynchronous, that duplicate names fail, or what the POLICY_MAX_FETCHES guardrail and force flag actually control.

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?

A single short sentence with zero filler, and the verb is front-loaded. It is efficient but underwritten—brevity here reflects missing content rather than disciplined editing.

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?

For a 15-parameter creation tool that spawns scheduled crawl jobs across two executor modes with guardrails and cron scheduling, one sentence is inadequate. The output schema and annotations cover return shape and safety, but nothing conveys the operational consequences of creating a policy.

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 100% and the 15 parameters are well documented inline, including executor modes, cron syntax, date_policy shapes, and the force guardrail override. The description adds no parameter meaning beyond the schema, which is the baseline-3 case.

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?

"Create a crawl policy" gives a specific verb and resource, so an agent knows the object being produced. It stops short of distinguishing the operation from policy_update or sibling creators like scope_create, leaving an agent to infer that this is the initial creation path.

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 description provides no when-to-use guidance: nothing about prerequisites, no mention of policy_update for modifying existing policies, and no note that a unique name is required. Usage must be inferred entirely from the sibling names and schema.

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