Skip to main content
Glama

server_governance

Read-onlyIdempotent

Expose the server's policy mode, write approval requirements, PII allowlist, and intentionally unimplemented tools so agents can verify governance rules without touching live data.

Instructions

This server's own policy: mode, approval requirement, PII allowlist, and the tools that are deliberately not implemented.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine value by disclosing that the response includes not just active policy but also a list of tools deliberately not implemented — a non-obvious trait that explains absent capabilities. It stops short of saying whether the returned policy is advisory or enforced.

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 short sentence fragment with no filler, front-loading the scope ('This server's own policy') before the content list. It is slightly under-specified rather than verbose; a leading verb would cost no length and improve parseability.

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 parameterless introspection tool with no output schema, the description covers the important ground by enumerating the returned fields, and annotations handle the safety profile. The remaining gap is how the agent should react to the reported mode or unimplemented-tool list, which the description does not spell out.

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 the baseline is 4 and there is nothing for the description to disambiguate. The schema (empty object, additionalProperties=false) already makes the no-argument contract unambiguous.

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 resource — this server's own policy — and enumerates its contents (mode, approval requirement, PII allowlist, deliberately unimplemented tools), which separates it from the contact-oriented siblings. It lacks an explicit verb (e.g., 'Returns'/'Reports'), so the reader must infer that this is a read-style introspection call rather than a configuration setter, but the resource is unmistakable.

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?

Usage is only implied: an agent can infer it should call this to learn the server's operating constraints before acting. There is no explicit when-to-use statement, no statement of when-not-to-use, and no pointer to an alternative such as rate_limit_status, which is the nearest adjacent introspection tool.

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