Escalate Anything

Overview Schema Source Related Servers Discussions Admin

Find a company

find_company

Read-only

Find a company by name, brand, or alias to retrieve its complaint and escalation playbook. Use an empty query to list all supported companies, optionally filtered by sector.

Instructions

Find companies by name, brand or alias (e.g. 'xfinity', 'united', 'chase'). With an empty query, list every company, optionally only one sector.

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

Input Schema

Name	Required	Description	Default
`query`	No
`sector`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Nov 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact — an empty query returns the entire company set — but says nothing about result size, pagination, ranking/ambiguity handling, or what happens with multiple matches, which matters for a broad search tool.

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?

Two sentences, zero filler, with the primary matching behavior front-loaded ahead of the edge-case empty-query path. The parenthetical examples earn their place by disambiguating brand/alias matching.

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?

An output schema exists, so return shape needn't be explained, and both parameters are accounted for. For a two-param read-only lookup this is close to complete; only ambiguity/ranking behavior and sector value guidance are missing.

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 description coverage is 0%, so the description carries the burden and does add meaning: the query matches on name, brand, or alias, and an empty string is a deliberate list-all trigger rather than a no-op. Sector is described only as an optional narrowing filter, with no accepted values or format, which is the main remaining gap.

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 gives a specific verb+resource ("Find companies") and defines matching semantics (name, brand, or alias) with concrete examples like 'xfinity' and 'chase'. It also states the empty-query behavior, but never contrasts itself with the sibling get_company, so an agent must infer the difference between lookup-by-search and lookup-by-id.

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

Usage Guidelines4/5

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

It clearly explains the no-query path ("With an empty query, list every company, optionally only one sector"), which is real when-to-use guidance for both the search and enumeration modes. It stops short of naming alternatives such as get_company or saying when this is the wrong tool, so it lands at clear context without exclusions.

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