Skip to main content
Glama

policy_list

Read-onlyIdempotent

Lists crawl policies and filters them by enabled status, so agents can quickly identify which policies are active or disabled.

Instructions

List crawl policies. Optional filter by enabled status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "policy_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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 declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — no pagination, ordering, result limits, or volume characteristics for a listing operation, and an output schema exists so return shape need not be described.

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 core action and with no filler. Nothing is redundant, though the second sentence is a bare fragment rather than integrated guidance.

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?

For a trivial one-parameter read tool with a full output schema and rich annotations, the definition is largely sufficient. It leaves open whether results are paginated or capped and how this relates to the other policy_* tools, which matters for a list endpoint.

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 0%, so the description must carry the single parameter, and "Optional filter by enabled status" does explain its purpose and optionality. It stops short of spelling out that true/false narrow the list while null/omitted returns everything, which is the one distinction an agent might want.

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 ("List crawl policies"), which is unmistakable. It does not differentiate itself from siblings such as policy_get or policy_runs, but the list semantics are clear without opening the schema.

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 hint is that the filter is optional; there is no statement of when to use this instead of policy_get for a single policy or when enabled filtering matters. The reader must infer the browse-all use case.

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