Skip to main content
Glama

Search external parties

search-external-parties
Read-onlyIdempotent

Search the account's external parties (people and businesses that appear on documents) by name.

External parties are the counterparties on documents — the entities on the OTHER side of an agreement, which do not belong to the account. They are distinct from account parties, which are the account's own entities (the company the user belongs to and its subsidiaries / group companies). Phrasing like "our", "we", "us", "my company" or "our subsidiary" refers to an account party, not an external party — in that case use list-account-parties instead.

Use this tool when:

  • You need a party's name to filter list-documents by external party

  • You want to find parties matching a search term

Matches the party's name (entity_name). Results are capped and de-duplicated by name, so narrow the query if you don't find who you're looking for. If you are looking for a named entity and it does not appear here, it may be an account party (the account's own side) instead — try list-account-parties before concluding it does not exist.

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": {
      "query": "<query>"
    },
    "name": "search-external-parties"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of external parties to return (default and max: 25)
queryYesSearch term matched against external party names (case-insensitive, min 3 characters)

Output Schema

NameRequiredDescriptionDefault
external_partiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so safety is covered. The description adds genuinely non-obvious behavior: matching is against entity_name only, results are capped and de-duplicated by name, and a miss may mean the party lives on the account side. It stops short of describing ordering or what a hit contains, though the output schema covers returns.

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?

Front-loaded with the core action, then a definition paragraph, then scannable bullets. The account-party versus external-party explanation is longer than strictly necessary but earns its place by preventing the single most likely confusion; overall still efficient.

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 two-parameter search tool with full schema descriptions, annotations and an output schema, nothing an agent needs to call it correctly is missing: what it searches, the cap, the de-duplication, the failure mode, and the sibling to try instead.

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 coverage is 100%, so baseline is 3; the description goes further by naming the matched field (entity_name) and giving actionable advice to narrow the query when the cap or de-duplication hides a result. That is real meaning beyond the schema's type/length constraints.

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 and resource ('Search the account's external parties ... by name') and immediately defines what an external party is versus an account party, which is the key disambiguation against the sibling list-account-parties. An agent can pick this tool without opening the schema.

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

Usage Guidelines5/5

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

Explicit 'Use this tool when' bullets cover both use cases (getting a name to filter list-documents, finding matching parties), and the description names the alternative list-account-parties with the exact trigger phrases ('our', 'we', 'us', 'my company') that should route the agent elsewhere. It also prescribes a fallback when a name is not found.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources