Phoenix/rebrand relink detection: links a debarred principal to a newly-formed business entity.
Scored across 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clearly defined and distinct.
Since there is only one tool, naming consistency is not applicable; the single name follows a descriptive pattern.
One tool is minimal but acceptable for a highly specialized compliance-check server. However, it feels thin for a general screening server.
The tool provides a thorough evidence chain for phoenix/rebrand detection, covering the core function. Missing complementary tools like entity lookup or watchlist search are minor gaps.
Detect a phoenix / rebrand relink that exact-match screeners miss. Given a principal or entity name (e.g. a debarred contractor, an excluded provider, or an OFAC-listed party), this fuzzy-relinks it to NEWLY-FORMED Secretary-of-State business entities that share the name AND a second independent signal (principal address or named registered agent), while filtering out shared commercial registered-agent addresses. Returns NON-CONCLUSORY review flags with the full evidence chain and primary-source links — a research lead for human diligence, never a determination of wrongdoing. Use during M&A diligence, vendor/counterparty onboarding, or compliance screening.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Principal or entity name to check for phoenix relinks (e.g. a debarred/excluded/sanctioned party). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully discloses behavioral traits: it returns non-conclusory review flags with full evidence chain and primary-source links, filters out shared commercial registered-agent addresses, and positions the output as a research lead for human diligence. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is somewhat lengthy but each sentence adds value, and the main purpose is front-loaded. It could be slightly more concise without losing key information, but overall it is well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description thoroughly explains return values (non-conclusory review flags, evidence chain, links) and the matching logic. For a single-parameter tool, it provides complete context for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already covers the single parameter 'name' with a description. The tool description adds contextual examples (e.g., 'a debarred/excluded/sanctioned party') but does not provide substantial new meaning beyond the schema. Baseline 3 is appropriate due to high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool detects phoenix/rebrand relinks that exact-match screeners miss, specifies the input (principal or entity name), and describes the fuzzy matching logic. It distinguishes itself from exact-match screeners, making the purpose specific and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool ('Use during M&A diligence, vendor/counterparty onboarding, or compliance screening') and clarifies what it does not do (returns non-conclusory review flags, never a determination). This provides clear usage context and exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
phoenix_relink_checksos-entities — state business-entity registries in one normalised shape (fleet #2867).
Public-record + domain-graph lookup. Not universal SMB. US-eligible. x402 POST /v1/enrich.
Company hierarchy analysis and address verification via MCP
UK company lookup, LEIs and sanctions name matching for agents, with source provenance.
Add one secure layer between your agents and this server.
