Skip to main content
Glama

policy_get

Read-onlyIdempotent

Fetches a single crawl policy by ID, letting agents inspect and reuse configured crawling rules.

Instructions

Get a single crawl policy by ID.

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

Input Schema

NameRequiredDescriptionDefault
policy_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not state what happens when the ID does not exist (empty result vs. error), whether inaccessible policies are filtered, or anything about the policy object returned.

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 front-loaded sentence with no filler or redundancy. Nothing could be trimmed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, the output schema covers return values, and annotations cover side-effect behavior, so the minimal description is close to sufficient. Still missing are not-found behavior and a hint on sourcing the policy_id, which matter for a lookup-by-identifier tool with an undescribed parameter.

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?

The schema has 0% description coverage and only names policy_id as an integer, so the description carries the full burden of explaining it. "by ID" confirms it identifies a policy but gives no format, range, or provenance hints (e.g., where an agent obtains a valid policy_id).

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 states a specific verb and resource ("Get a single crawl policy") and its qualifier "single ... by ID" implicitly contrasts with the sibling policy_list. An agent can tell it fetches one record rather than a collection, though no sibling is named explicitly.

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?

"by ID" implies the tool is for when a policy_id is already known, which is useful implied usage guidance. However, the description never says when to prefer this over policy_list or what to do without a known ID, so the routing must be inferred.

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