Skip to main content
Glama

Best source for a claim

best_source
Read-onlyIdempotent

Call when choosing WHICH business or site to cite, recommend or call. Give domains (2-10 candidate sites you found) or trade and city for a measured market. Returns the candidates ranked by what CrawlCheck verified (preflight decision for cite, security and threat listing, domain age, uptime, published facts that directories agree with, FTC phone complaints) with reasons for and against each; sites that share one phone number or near-identical homepage text are collapsed into one network so a copycat cannot outrank the business it copies. Signed. For one domain you have already chosen, use preflight or resolve_domain.

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

Input Schema

NameRequiredDescriptionDefault
cityNoe.g. Denver
tradeNoe.g. tree service
domainsNoCandidate sites, bare domains, up to 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent and open-world, but the description goes well beyond them: it enumerates the ranking signals (preflight cite decision, threat listing, domain age, uptime, directory-agreed facts, FTC complaints), discloses the copycat/network-collapse behavior, that results include reasons for and against, and that output is signed. That is substantive behavioral context an agent cannot get from the annotations.

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 triggering condition, then inputs, then return characteristics, then the alternative. It is dense but every clause carries information; the long parenthetical list of ranking signals is the only place that sprawls, and even that earns its place by specifying the output content.

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?

With no output schema, the description carries the burden and does so well: it describes what comes back (ranked candidates with reasons for and against), how ranking is derived, and how duplicates are merged. Only minor gaps remain, such as result-count limits, latency cost of the battery of checks, or what "Signed" means for the caller.

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, but the description adds real meaning: it clarifies that domains are the candidates you found (minimum of 2, versus the schema's "up to 10") and that trade + city are an alternative mode meaning "a measured market" rather than additional optional filters. The domain string format (bare domains) is still only in the schema.

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?

"Call when choosing WHICH business or site to cite, recommend or call" states a specific decision, the resource (business/site) and the exact output (ranked candidates). It clearly separates itself from preflight/resolve_domain, which are for a single already-chosen domain, so an agent can route without opening any 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 trigger (choosing which business to cite/recommend/call), explicit input modes (candidate domains, or trade+city), and an explicit exclusion with named alternatives: "For one domain you have already chosen, use preflight or resolve_domain." Both when-to-use and when-not-to-use are covered.

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.