Skip to main content
Glama
Sign In

CallForMe

by tel.callforme
OverviewDiscussionsAdmin

Find a business

find_business
Read-onlyIdempotent

Find a US or Canadian business's phone number, address, whether it's open now, today's hours, local time and rating. Pass near (city and state or province, or a zip or postal code); without it results can be anywhere in the US. No account needed. Also finds CallForMe's free fictional demo lines by name (demo: true, cost "Free"), e.g. query "Maple Street Pizza" or "demo". Example: find_business(query="brake repair", near="Plano, TX").

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
nearNoCity and state or province, neighborhood, zip or postal code, or address
limitNo1-10, default 5
queryYesA name or type, e.g. "auto repair", "Nonna's Trattoria", "CVS pharmacy"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / near / description
      Previous value: -"City and state, neighborhood, zip, or address"New value: +"City and state or province, neighborhood, zip or postal code, or address"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond that: geographic scope limits (US/Canada), the consequence of omitting `near`, no-auth requirement, and the demo-line flag with cost 'Free'. Return-shape detail is left implicit, which is acceptable since there is no output schema but the field list is enumerated.

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-loads the capability and return fields, then the geo-scoping rule, then the demo-line edge case, then an example. Dense but no dead sentences; the parenthetical brand reference ('CallForMe's') is slightly incidental but tied to the demo feature.

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?

For a read-only, single-object lookup with a fully described 3-param schema and no output schema, the description covers scope, auth, and edge-case behavior adequately. Only pagination/result-count semantics for `limit` are unaddressed, a minor gap.

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 a 3 baseline applies, but the description goes further by explaining the behavioral effect of `near` (unscoped results can be anywhere in the US) and by providing a concrete worked example for `query` + `near`. It does not mention `limit` at all, which the schema already covers.

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 concrete verb and resource ('Find a US or Canadian business') and enumerates the specific fields returned (phone, address, open-now status, hours, local time, rating). This is clearly a business lookup, distinct from the call-management siblings like place_call, list_calls, or call_around.

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?

Gives explicit operational guidance: pass `near` to geo-scope results, otherwise results can be anywhere in the US, and notes no account is required. It also explains a secondary mode (demo lines via query 'demo'). It stops short of naming a sibling alternative for cases this tool doesn't cover.

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

All CallForMe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources