Skip to main content
Glama

policy_estimate

Idempotent

Estimates the fetch count a policy payload will require, flagging unroutable and unmapped concepts so panel editors can validate coverage before saving.

Instructions

Estimate the fetch count for a policy payload (used by the panel editor).

Returns {"estimate": int, "unroutable": [...], "unmapped": [...], "policy_max_fetches": int}.

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

Input Schema

NameRequiredDescriptionDefault
modeNoper_date
frequencyNodaily
entity_idsNo
concept_idsYes
date_policyNo
entity_typeYes
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 idempotent=true, destructive=false, openWorld=false, so safety is largely covered. The description adds that this is a non-mutating-looking computation despite readOnlyHint=false, and it names the return keys, but it does not explain why a read-like estimate is annotated non-readOnly, nor does it describe cost or latency. The return-key listing duplicates the output schema, so credit is limited.

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, front-loaded sentences with no filler; purpose comes first and the return shape second. The return-shape sentence is somewhat redundant with the output schema, but it is compact and not harmful.

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 7-parameter tool with zero schema description coverage, the definition is thin: an agent knows it estimates a cost but not how mode/frequency/date_policy/source_filter shape the number, nor what qualifies a concept as unroutable or unmapped. The output schema covers return values, but input semantics and the readOnlyHint=false tension are unaddressed.

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 7 parameters, so the schema gives only names and types. The description mentions 'policy payload', 'fetch count', and the ambiguous 'unroutable'/'unmapped', but never explains mode, frequency, entity_type, date_policy, source_filter, or what makes an entity unroutable. The parameters that dominate the estimate remain opaque.

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+resource: 'estimate the fetch count for a policy payload'. An agent can tell this is a dry-run cost estimator rather than a policy mutation, which separates it from policy_create/policy_update/policy_get. It stops short of 5 because it never names or contrasts a sibling it could be confused with (e.g. policy_get or coverage_report).

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 only usage cue is the parenthetical '(used by the panel editor)', which names a caller rather than a condition. There is no statement of when an agent should run an estimate versus just creating/updating a policy, and no exclusions or prerequisites.

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