Skip to main content
Glama

security-crypto

csp_parse_and_audit

Parse, build, or security-audit Content-Security-Policy (CSP) headers for unsafe-inline, unsafe-eval, wildcard sources, and missing frame-ancestors.

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

Input Schema

NameRequiredDescriptionDefault
textNo
policyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 behavioral burden. It discloses the audit checks performed, which is useful, but says nothing about whether parsing and building are local transformations, what they return, whether any inputs are required, or how errors are handled.

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 definition is a single front-loaded sentence with no filler or repetition. Its compression is efficient, though it contributes to the ambiguity around mode selection and parameter meaning.

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?

With no annotations, no output schema, and zero parameter documentation, the description is the only source of behavioral information. It covers the audit criteria but is not complete enough for a three-mode tool with two undocumented inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (text and policy) have 0% schema description coverage, and the description does not mention them at all. It provides no mapping between text versus policy inputs or the parse/build/audit modes, leaving the caller unable to determine what each field should contain.

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 (Content-Security-Policy headers) and specific operations (parse, build, security-audit), making the domain clear relative to sibling policy-audit tools. However, combining three distinct modes in one tool without indicating how the mode is selected leaves the exact operation ambiguous.

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?

It lists what the audit looks for (unsafe-inline, unsafe-eval, wildcard sources, missing frame-ancestors), which gives some implied usage context. But it provides no guidance on when to use this tool versus parsing/building, nor how it relates to sibling policy audit tools such as permissions_policy_audit or referrer_policy_audit.

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