Skip to main content
Glama

explain_policy

Explains in plain English what actions a secret's policy permits, helping users understand allowed API operations before use.

Instructions

Plain-English description of what you may do with a secret.

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": {
      "secret": "<secret>"
    },
    "name": "explain_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
secretYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It signals that the tool returns a plain-English explanation, but it does not state whether the operation is read-only, what permissions are required, how missing secrets are handled, or what the output looks like.

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?

The description is a single, front-loaded sentence with no wasted wording. It is appropriately concise, though its brevity contributes to gaps in other dimensions rather than making it poorly structured.

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

Completeness2/5

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

For a tool whose purpose is to explain policy, the description is quite thin. With no annotations, no output schema, and zero schema description coverage, an agent would benefit from more context about authentication needs, return format, and how the secret should be identified.

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 description coverage is 0%, and the only parameter is named 'secret'. The description mentions 'a secret' but adds no meaning about expected format, identifier type, or naming conventions beyond what the schema already provides.

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

Purpose3/5

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

The description says it provides a plain-English description of what you may do with a secret, which gives a general sense of the tool's purpose. However, it does not specify a verb+resource combination as precisely as a strong definition would, and it does not distinguish this tool from siblings such as list_secrets or request_access.

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 explicit when-to-use guidance, no when-not-to-use guidance, and no mention of alternatives. The description implies the tool is used to understand permissions for a secret, but it leaves the agent to infer that from the sentence alone.

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

Deploy Server

Other Tools