Skip to main content
Glama

security-crypto

cors_preflight_simulate

Simulate a browser CORS preflight check against Access-Control-Allow-Origin, Allow-Credentials, and Allow-Methods rules and flag RFC misconfigurations.

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

Input Schema

NameRequiredDescriptionDefault
methodNoPOST
allowOriginNo*
allowMethodsNoGET, POST, OPTIONS
requestOriginNohttps://app.example.com
allowCredentialsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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. 'Simulate' usefully signals that no real network request is made and nothing is mutated, but it doesn't say what the response looks like (pass/fail vs. a list of issues) or how inputs are interpreted, leaving meaningful behavioral gaps.

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 no filler. It leads with the action and follows with the rules checked, so every clause earns its place.

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?

A five-parameter tool with zero schema description coverage, no annotations, and no output schema needs far more: what the result contains, what requestOrigin/method mean, and how simulated values interact. The description is a one-line purpose statement only.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It does map three of five parameters to the named headers (allowOrigin, allowCredentials, allowMethods), but says nothing about requestOrigin or method, and adds no format or default guidance.

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

Purpose5/5

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

The description uses a specific verb ('Simulate') and resource ('a browser CORS preflight check'), and names the exact rules being evaluated (Allow-Origin, Allow-Credentials, Allow-Methods) plus the outcome ('flag RFC misconfigurations'). This is clearly distinguishable from the surrounding crypto/CSP/SSH audit siblings.

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 or when-not guidance, no prerequisites, and no named alternative. The phrase 'flag RFC misconfigurations' hints at an audit/debugging context, but the agent must infer that on its own.

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