Skip to main content
Glama

On call near a place

on_call_near
Read-onlyIdempotent

Emergency service businesses whose owner has switched on 'on call' right now (for a few hours at a time), nearest first, within a distance of a ZIP code or a point. Few owners use it yet: when none is on call, use search_businesses with emergency_now, which also covers posted 24/7 emergency service.

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

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, instead of a ZIP code.
lonNoLongitude, with lat.
zipNoA Connecticut or Massachusetts ZIP code.
milesNoHow far to look.
categoryNoOnly this trade.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral context: results are transient ('right now', 'for a few hours at a time'), coverage is sparse ('Few owners use it yet'), and ordering is nearest-first. It stops short of saying what an empty result looks like, but the sparsity warning effectively primes the agent for that.

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 tightly packed sentences: what it returns and how it is ordered first, the fallback second. No filler, and the most decision-relevant fact (low adoption, use the sibling when empty) is surfaced rather than buried.

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 lookup with full schema coverage and no output schema, the definition covers purpose, ordering, and fallback well. The one gap is that no parameter is required, so it never says what a call without zip or lat/lon does (e.g. defaults to the requester's location or fails) — relevant since miles silently defaults to 15.

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 100% and every parameter already carries a description, including the lat/lon-instead-of-zip relationship, so the baseline is 3. The description restates the zip-or-point alternative and distance scoping but adds no format, default, or edge-case detail beyond 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?

States a specific resource and scope: 'Emergency service businesses whose owner has switched on on call right now', with sort order ('nearest first') and geographic scoping ('within a distance of a ZIP code or a point'). This is clearly distinguishable from search_businesses, which the description itself frames as the broader alternative.

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 fallback rule: 'when none is on call, use search_businesses with emergency_now', and explains why that sibling is broader ('also covers posted 24/7 emergency service'). It does not spell out positive preconditions (e.g. 'use this when the caller needs someone immediately'), but the availability framing makes the use case clear.

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