IA-QA — 152 QA & Dev Tools for AI Agents

cors_test

Read-only

Audit a URL for CORS misconfigurations across several origins: wildcard with credentials, reflected origin, null origin, subdomain bypass, missing Vary. Returns risk level (safe/low/medium/high/critical) plus per-origin results. "unknown" means nothing was tested: every origin failed to connect, answered 5xx, or was refused with no CORS header (a 404, a firewall); never read it as "safe".

Input Schema

Name	Required	Description	Default
`url`	Yes	Full URL to test (e.g. https://api.example.com/endpoint)
`origin`	No	Custom Origin header to test (default: tests multiple origins automatically)

Output Schema

Name	Required	Description	Default
`url`	No
`error`	No
`tests`	No
`warning`	No
`risk_level`	No
`origins_tested`	No
`total_findings`	No
`origins_reachable`	No
`origins_conclusive`	No
`origins_inconclusive`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

addedInput schema / examples

Added value: +[
+  {
+    "origin": "https://other.example",
+    "url": "https://www.ia-qa.com/mcp"
+  }
+]

Changed6 schema fields changedAug 19, 2026
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / origins_conclusive
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / origins_inconclusive
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / origins_reachable
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / risk_level / enum
```
Added value: +[
+  "safe",
+  "low",
+  "medium",
+  "high",
+  "critical",
+  "unknown"
+]
```
- addedOutput schema / properties / warning
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedJun 21, 2026

addedOutput schema / properties

Added value: +{
+  "origins_tested": {
+    "type": "number"
+  },
+  "risk_level": {},
+  "tests": {},
+  "total_findings": {
+    "type": "number"
+  },
+  "url": {}
+}

Changed1 schema field changedJun 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedMay 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description goes meaningfully beyond that by disclosing the return vocabulary (safe/low/medium/high/critical plus per-origin results) and, critically, warning that "unknown" means nothing was tested and must never be read as "safe" — an anti-misinterpretation note that directly prevents a false negative. It does not explain why idempotentHint=false (results can differ between runs) or mention timing/rate considerations.

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?

Three dense sentences, zero filler, and the core action is front-loaded before the return semantics and the "unknown" caveat. Every sentence carries information an agent needs to act or to interpret output correctly.

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

Completeness4/5

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

With only two parameters, an output schema present, and annotations covering safety, the description is nearly complete: it explains the scan scope, the risk grading, and the failure-mode interpretation. The remaining gap is disambiguation from cors_checker, which matters for tool selection.

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 100%, so both parameters are already documented, including that omitting origin tests multiple origins automatically. The description's phrase "across several origins" and "per-origin results" restates this rather than adding new meaning; baseline 3 applies.

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?

States a specific verb and resource ("Audit a URL for CORS misconfigurations") and enumerates the concrete checks performed: wildcard with credentials, reflected origin, null origin, subdomain bypass, missing Vary. It does not, however, differentiate itself from the very similar sibling cors_checker, leaving the agent to guess which of the two CORS tools to pick.

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

Usage Guidelines3/5

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

Usage is implied by the verb and the required url parameter, but there is no explicit when-to-use / when-not guidance and no named alternative. The presence of a near-duplicate sibling (cors_checker) makes this omission more costly than it would otherwise be.

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

All IA-QA — 152 QA & Dev Tools for AI Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.