Skip to main content
Glama

linepref: check before an AI agent calls a business

Check a business number before calling

check_before_call
Read-only

Call this BEFORE placing a phone call to a business. It often saves the call entirely: in testing, 41% of real businesses could be handled through an online booking link instead of a call. Returns whether the business can be booked or reached online instead (with the link), whether it has asked not to receive AI calls, whether this caller has been opted out, and pooled call data from other callers (answer rate, hold time, phone-menu path, best hours). advice is one of: use_link, do_not_call, call, unknown.

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": {
      "number": "<number>"
    },
    "name": "check_before_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoBusiness name, if known
numberYesPhone number, E.164 preferred (+15125550100)
countryNoISO country code, only needed for national-format numbers (US, CA, AU, NZ, GB, IE)
websiteNoThe business's website, if known. Enables the online-booking check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description goes far beyond that by enumerating exactly what the response contains – online booking link, business-level do-not-call request, caller-specific opt-out, and pooled caller data (answer rate, hold time, menu path, best hours). It also defines the advice enum values (use_link, do_not_call, call, unknown), which removes any ambiguity about how to act on the result.

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?

Front-loads the imperative instruction, then justifies it with a single statistic, then enumerates the return payload. Every sentence earns its place and there is no restatement of the name or title.

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?

No output schema exists, so the description must carry the return-value burden, and it does so thoroughly, including enum semantics. Minor gaps remain: it does not say how stale pooled call data may be, nor what action to take when advice is 'unknown'.

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 description coverage is 100%, so all four parameters are already documented in the schema itself, including that website enables the online-booking check. The description adds context about why the number matters (opt-out is per-caller, data is pooled across callers) but gives no new syntax or precedence rules beyond the schema. Baseline 3 applies.

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 check (whether a business can be booked or reached online) on a specific resource (a business phone number), plus the timing constraint 'BEFORE placing a phone call'. The verb+resource+scope combination is unambiguous and naturally separates it from post-call siblings like report_call_outcome.

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 an explicit trigger ('call this BEFORE placing a phone call to a business') backed by a quantified payoff (41% handled via online booking link). It does not name sibling alternatives such as check_many for batch lookups or state when not to use it, so it stops short of full routing guidance.

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