Escalate Anything

Overview Schema Source Related Servers Discussions Admin

Find regulators

find_regulators

Read-only

Identifies federal regulators and state agencies that accept complaints for a specific sector and optional state, so you can route an escalation to the right authority.

Instructions

Federal regulators and state agencies that take complaints for a sector.

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": {
      "sector": "<sector>"
    },
    "name": "find_regulators"
  }
}

Input Schema

Name	Required	Description	Default
`state`	No
`sector`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Nov 13, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds domain context by saying these are agencies that take complaints, but it does not describe search behavior, data freshness, or result scope beyond the sector framing.

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 description is a single short sentence with no wasted wording and the core resource is front-loaded. It is efficient, though the terseness contributes to gaps elsewhere.

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?

An output schema and annotations cover return values and safety, so the description need not explain those. However, for a two-parameter lookup with zero schema description coverage, leaving the state parameter entirely unexplained is a clear completeness gap.

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

Parameters2/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 carry parameter meaning. It mentions the sector filter but never explains the optional state parameter, such as whether it narrows results to state-level agencies or what value format is expected.

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 identifies a specific resource: federal regulators and state agencies that accept complaints for a sector. That is clear enough to distinguish it from siblings like find_company or scam_check, but it is a noun phrase rather than an explicit verb+resource statement and does not explicitly say it returns a list.

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 guidance, no when-not-to-use guidance, and no named alternative. The only implied usage is that an agent would call this to locate complaint-receiving agencies for a sector, which is thin.

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