Red Center Studio free tools

Single point of failure scan

spof_scan

Read-only

Find which companies a business depends on for email, sign-in, DNS, website hosting, outbound email and SaaS, using public DNS only, and what a single outage would stop. Returns the layers, the vendors, a risk score and recommendations. Free, no key. Rate limited per connection and to about 20 fresh scans an hour; repeat scans of the same domain within an hour come from cache.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "spof_scan"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	The business domain, for example example.com.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it names the data source (public DNS only), what is returned (layers, vendors, risk score, recommendations), cost and auth (free, no key), and concrete rate limits (per connection, ~20 fresh scans/hour, cached repeats within an hour). That operational detail is exactly what an agent needs before calling.

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?

Two sentences, front-loaded with purpose then behaviour, with no filler. The final sentence packs cost, rate limits and caching tightly; it borders on cramming several distinct facts into one clause but stays readable.

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?

For a single-parameter, no-output-schema tool, the definition covers source, cost, limits, caching and the shape of the result, so an agent knows what it gets back without an output schema. Nothing material for correct invocation is missing.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already defines 'domain' with an example. The description adds no format or validation meaning beyond it (e.g. whether subdomains, URLs or bare domains are accepted), leaving it at the high-coverage baseline.

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?

States a specific verb (find) and resource (companies a business depends on) and enumerates the exact layers covered: email, sign-in, DNS, website hosting, outbound email and SaaS. The data source ('public DNS only') and the deliverable ('what a single outage would stop') make it immediately distinguishable from siblings like decode_error and geo_audit.

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 purpose (dependency/outage-risk discovery) but never stated explicitly as when-to-use, when-not-to-use, or relative to the sibling tools. The rate-limit and no-key notes help an agent decide it can call it, but there is no routing guidance.

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

All Red Center Studio free tools 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.

Resources

Need Help?