Skip to main content
Glama

list_policies

List the ToS risk policies available to you: the built-in system policies (standard, strict, procurement) plus any custom policies you have created. Pass a policy id as policy_id to any scan tool to judge vendors by your principal's rules instead of the default.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the composition of the result set (three named built-ins plus custom policies) and the key behavioral trait that returned ids are consumable by scan tools, but says nothing about ordering, pagination, whether custom policies require creation first, or permissions. The output schema covers the return shape, which offsets part of the gap.

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?

Three short sentences, front-loaded with what the tool returns and followed by the actionable next step. Every sentence contributes; nothing is repeated from the schema or title.

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

Completeness4/5

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

For a zero-parameter read-only list with an output schema, the description covers content, the built-in/custom distinction, and downstream usage. Only minor operational details (ordering, whether the list can be empty, auth requirements for custom policies) are absent.

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, which sets the baseline at 4. The description goes slightly further by explaining where policy_id values for other tools come from, adding cross-tool meaning, though it does not describe this tool's own (empty) argument object.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the ToS risk policies") and enumerates exactly what comes back: built-in system policies (standard, strict, procurement) plus custom ones. An agent can distinguish this read-only listing from create_policy or the scan tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives concrete downstream guidance: take a returned id and pass it as policy_id to any scan tool to override default judging rules. That is a clear 'what to do with this' instruction, but it stops short of naming alternatives such as create_policy for adding custom policies or stating when listing is unnecessary.

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.