Skip to main content
Glama

ARL Protocol

arl_list_policies

The built-in arl-policy/1 verification policies with their hashes: which workload classes, tiers, committee sizes, windows and evidence each allows.

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": "arl_list_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full load, and it does disclose what is returned: built-in (non-user-editable) policies plus their hashes and the constraints each encodes. It does not say the operation is read-only, whether results are ordered or paginated, or that no arguments are accepted, so meaningful behavioral gaps remain.

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 front-loaded sentence with a colon-delimited enumeration of the returned attributes; nothing is padded. The phrase 'built-in arl-policy/1 verification policies with their hashes' is slightly circular but each clause conveys 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?

For a zero-argument listing tool with no output schema and no annotations, the description reasonably covers what comes back, so return-value explanation is adequate. It omits how many policies exist, ordering, and the read-only nature, which an agent would still want to know before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description's enumeration of returned fields adds useful meaning without overstepping into schema territory.

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 identifies a specific resource — the built-in arl-policy/1 verification policies and their hashes — and even enumerates the per-policy fields returned (workload classes, tiers, committee sizes, windows, evidence). The verb 'list' is only implied by the name rather than stated, and it never contrasts itself with the adjacent arl_list_validators, so it stops short of a 5.

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?

There is no statement of when to call this versus alternatives such as arl_list_validators, nor any prerequisite or exclusion. The use case (discovering which built-in policies exist and their hashes) is only inferable from the description's content, not stated as guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.