Skip to main content
Glama

Pumpkin

find_business

Read-only

Find a participating business by its name, site ID or website domain. Use its returned site ID for other tools.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world lookup, so the safety profile is covered. The description usefully adds that only *participating* businesses are returned and that the result is keyed by site ID, but says nothing about no-match behavior, ambiguity/multiple results, or matching semantics.

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 short sentences, zero filler, with the lookup keys plus the downstream hand-off compressed into the front. Nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining the return value, and it only names the site ID field rather than the full useful shape. For a one-parameter lookup tool this is close to adequate, but an agent still cannot predict the response structure or the failure mode.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the single `query` param is documented only as a max-200-char string. The description compensates by enumerating the three accepted value forms (name, site ID, website domain), which is real added meaning, but leaves open whether matching is exact, prefix, or fuzzy.

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?

A specific verb ("Find") plus a specific resource ("participating business") and the three accepted lookup keys (name, site ID, domain). It is clearly distinct from data-fetching siblings like site_get or get_locations, though it does not name a sibling it might be confused with.

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?

The second sentence gives explicit sequencing guidance — resolve to a business here, then feed the returned site ID into other tools — which is exactly the ordering an agent needs. It stops short of stating exclusions, e.g. what to do if the business is not participating or a search returns multiple matches.

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