Skip to main content
Glama

security-crypto

permissions_policy_audit

Parse or build HTTP Permissions-Policy feature allowlists (camera, microphone, geolocation, usb, payment) and flag wildcard feature exposure.

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

Input Schema

NameRequiredDescriptionDefault
textNo
policyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add real behavioral information beyond the name: the tool flags wildcard feature exposure, which signals an analysis/warning behavior. However, it does not clarify that parsing is read-only while building produces output, nor does it describe the return format or any limits.

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?

A single front-loaded sentence with the resource first and the distinctive wildcard-flagging behavior last. No filler, no restatement of the tool name.

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 two-mode tool with two undocumented parameters, no annotations, and no output schema, the description is too thin. An agent still cannot tell which parameter drives which mode or what the tool returns when it flags exposure.

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 0% and neither 'text' nor 'policy' is mentioned or explained in the description. At best the 'parse or build' phrasing loosely implies one parameter is input text and the other is a policy to construct, but the mapping is left entirely to inference.

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 uses concrete verbs (parse, build, flag) against a specific resource (HTTP Permissions-Policy feature allowlists) and even enumerates the features handled. An agent can distinguish it from sibling audits like referrer_policy_audit or csp_parse_and_audit by the header type, though the description never states that differentiation explicitly.

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?

'Parse or build' hints at two modes but the description never says when to choose one over the other, what inputs each mode expects, or when this tool is preferable to another header-audit sibling. No prerequisites or exclusions are given.

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