Skip to main content
Glama

drwho.me

by me.drwho
OverviewAdmin

dossier_cors

Core dossier check: Send a CORS preflight OPTIONS request to https:/// and return the access-control-* response headers. Use to verify CORS policy for a specific origin-method pair, or to check whether a domain allows cross-origin requests; provide origin and method to simulate a precise preflight, or omit to use defaults (origin: https://domainposture.com, method: GET). Single OPTIONS request via fetch, 5 s timeout. Returns a CheckResult: on success, {status:"ok", headers:{access-control-allow-origin,...}}; on failure, {status:"error", reason}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesPublic FQDN, e.g. example.com. Must be resolvable on the public internet; IPs, ports, paths, and protocol prefixes are rejected.
methodNoAccess-Control-Request-Method header value, e.g. POST or PUT. Defaults to GET if omitted.
originNoOrigin header value to include in the preflight, e.g. https://app.example.com. Defaults to https://domainposture.com if omitted.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / origin / description
      Previous value: -"Origin header value to include in the preflight, e.g. https://app.example.com. Defaults to https://drwho.me if omitted."New value: +"Origin header value to include in the preflight, e.g. https://app.example.com. Defaults to https://domainposture.com if omitted."
  2. Changed3 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Public FQDN."New value: +"Public FQDN, e.g. example.com. Must be resolvable on the public internet; IPs, ports, paths, and protocol prefixes are rejected."
    • changedInput schema / properties / method / description
      Previous value: -"Access-Control-Request-Method; default GET"New value: +"Access-Control-Request-Method header value, e.g. POST or PUT. Defaults to GET if omitted."
    • changedInput schema / properties / origin / description
      Previous value: -"Origin header to send; default https://drwho.me"New value: +"Origin header value to include in the preflight, e.g. https://app.example.com. Defaults to https://drwho.me if omitted."
  3. Added

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description must disclose behavior, and it does: single OPTIONS request via fetch, 5s timeout, and the exact success/failure CheckResult shape. It could mention rate limits or side effects, but for a read-only network check, this is strong transparency.

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?

The description is concise and front-loaded with 'Core dossier check: ...' then expands logically. No filler; every sentence contributes purpose, usage, behavior, or return format.

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

Completeness5/5

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

The tool has no output schema, so the description must explain return values; it does. It covers purpose, behavior, parameters, defaults, and success/failure shapes, making it self-contained for a simple 3-parameter tool.

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?

Schema coverage is 100%, so baseline is 3. The description adds semantic value by explaining the effect of providing or omitting origin/method ('simulate a precise preflight') and defaults, going slightly beyond schema descriptions.

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 clearly states the tool's purpose: 'Send a CORS preflight OPTIONS request to https://<domain>/ and return the access-control-* response headers.' It specifies a precise verb (send/return), resource (CORS preflight), and scope, distinguishing it from sibling DNS/TLS tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use: 'Use to verify CORS policy for a specific origin-method pair, or to check whether a domain allows cross-origin requests.' It also provides guidance on parameters: 'provide origin and method to simulate a precise preflight, or omit to use defaults.' This is clear usage direction.

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

All drwho.me toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources