Samuelz® Policy

Unternehmensregeln auflisten

list_policies

Read-onlyIdempotent

Find recorded policy/template identities before reading content or history. Use get_policy for a verified snapshot, get_policy_history for comparisons, and get_policy_write_options for editable settings, including unconfigured native adapters.

Counts reflect stored history, not successful attestation. Pages are live: new confirmations can shift results. Retain the returned cursor until hasMore=false; a goal cursor or history offset is invalid here.

Requires policy:read and current policies Owner access. Invalid/foreign cursors and access loss fail; reading changes no settings or permissions.

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

Name	Required	Description	Default
`cursor`	No	Unchanged pagination.nextCursor from this workspace’s previous list_policies page. Omit for the first page; do not use a goal cursor or a history version offset.

Output Schema

Name	Required	Description
`rules`	Yes	Up to 200 recorded identities ordered by moduleKey, policyKey, kind. Counts are stored history, not verified values or write authority.
`tenantId`	Yes
`moreRules`	Yes
`pagination`	Yes
`writeOptions`	Yes	Existing native/FULL editable-adapter descriptors. Business discovery uses get_policy_write_options instead.
`grantsActionAuthority`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the description is free to add what they cannot: that counts reflect stored history rather than attestation, that pages are live and can shift as confirmations arrive, that the cursor must be retained until hasMore=false, and the exact auth requirements (policy:read plus Owner access) and failure modes (invalid/foreign cursors, access loss). The 'pages are live' caveat usefully qualifies the idempotentHint without contradicting it, since it concerns result volatility rather than side effects; only a note on the returned page shape is missing, and the output schema covers that.

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 tight paragraphs ordered by what an agent needs first: what it is and what it is not, then behavioral caveats, then preconditions and failure modes. No sentence is filler, including the access-loss clause.

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

Completeness5/5

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

For a single-parameter paginated list tool with an output schema, everything an agent needs to call it correctly is present: discovery role, sibling routing, auth, pagination discipline, and failure conditions. Return-value explanation is correctly left to the output schema.

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?

With one parameter at 100% schema coverage the baseline is 3, and the description goes beyond it by pinning the cursor to 'unchanged pagination.nextCursor from this workspace's previous list_policies page' and explicitly excluding goal cursors and history version offsets — a cross-tool distinction the schema only partially encodes.

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 ('Find recorded policy/template identities') plus a scope qualifier ('before reading content or history') that tells an agent this is the discovery step, not the content read. It then names three sibling tools it is not, so the boundary is unambiguous 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 Guidelines5/5

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

Explicitly routes the agent: get_policy for a verified snapshot, get_policy_history for comparisons, get_policy_write_options for editable settings (including unconfigured native adapters). Each alternative carries the condition that selects it, leaving nothing to inference.

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

All Samuelz® Policy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?