Skip to main content
Glama

Policy: who has signed

policy_status
Read-only

Who acknowledged the current version of a policy and who is still missing. This is the evidence auditors ask for. Requires the organization API key.

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

Input Schema

NameRequiredDescriptionDefault
policy_idYes
required_peopleNoEveryone who must sign; Privi lists who is missing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the important non-schema fact that an organization API key is required, which an agent cannot learn from the annotations. The audit-evidence framing also signals the results are authoritative rather than advisory. It does not describe result shape or whether missing signers are omitted vs empty-listed.

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?

Three short sentences, front-loaded with the result the tool returns, then the value proposition, then the prerequisite. Nothing is redundant. The auditor sentence is partly persuasive framing rather than spec, which keeps it off a 5.

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 read-only, two-parameter tool with no output schema, the description conveys what the tool answers, that it is scoped to the current version, and the auth requirement — enough to call it correctly. The remaining gap is that it never says how to interpret an empty or absent required_people argument.

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?

Schema coverage is only 50%, so the description needs to carry some parameter weight and it does not. policy_id is never explained beyond 'the current version of a policy', and required_people — the parameter that determines whether the tool computes a 'missing' list — is not mentioned at all; only the schema itself documents it. The description adds essentially no meaning beyond the schema.

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 precise resource and a two-part result: acknowledgement of the *current version* of a policy, and who is still missing. That is far more specific than a bare 'status' tool and lets an agent separate it from policy_acknowledge or approval_status without opening a schema. It stops short of explicitly naming the sibling that handles the opposite action.

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?

'This is the evidence auditors ask for' implies the compliance/audit use case and hints at when to reach for it, and the API-key requirement is a real prerequisite. But there is no explicit when-not or named alternative (e.g. approval_status, policy_acknowledge), so selection still requires inference from the name.

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.

Resources