Skip to main content
Glama

ILIT Society - directory of allergists offering intralymphatic immunotherapy

find_practitioners

Read-onlyIdempotent

Search the directory of allergists offering ILIT. Give a zip code, a city, "City, ST", a state name or code, or coordinates. Results come nearest first with the distance in miles; a 50-mile radius splits "within" from "further", but people travel far for ILIT, so always show the closest ones even when none is within the radius. Optional filters: allergen, accepting new patients, treats children, video first consult.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 10, max 50).
queryNoZip code, city, "City, ST", or a US state (name or two-letter code). Leave empty to list everything.
allergenNoAn allergen name or slug (grass pollen, tree pollen, ragweed, dust mite, cat, dog, mold, …).
latitudeNoWith longitude: search around coordinates instead of a query.
longitudeNo
radius_milesNoDefault 50.
treats_childrenNoOnly listings that treat children.
video_first_consultNoOnly listings offering a video first consult.
accepting_new_patientsNoOnly listings currently accepting new patients.

Output Schema

NameRequiredDescriptionDefault
totalYes
originNo
furtherNo
resultsYes
within_radiusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, non-destructive query, so the description's job is to add result-shape context, which it does: results come nearest-first with distances in miles and a 50-mile radius splits 'within' from 'further'. It also flags the domain-specific expectation that users travel far for ILIT, which materially affects how results should be presented. It does not discuss pagination or limits, keeping it short of a 5.

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?

Three sentences, front-loaded with purpose, then inputs, then result behavior, with no filler. The radius/travel sentence is longer than strictly necessary but carries genuine presentation guidance that affects how the agent should handle empty-radius results.

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

Completeness5/5

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

An output schema exists, so return values need not be described, and the description covers the remaining essentials: accepted location input forms, result ordering, distance units, radius semantics, and the optional filters. An agent can call this correctly and interpret the response without further context.

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 89%, so the schema already documents query formats, allergen, radius, and the boolean filters. The description restates the location input formats and names four of the optional filters, but adds no semantics the schema lacks and omits limit and the latitude/longitude pairing. Baseline 3 applies when the schema does the heavy lifting.

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?

The description opens with a specific verb and resource: 'Search the directory of allergists offering ILIT', which is clearly a search operation distinct from retrieval tools like get_practitioner or listing tools like list_practices. It does not explicitly name a sibling or state what makes it different from them, so it lands just short of the top mark.

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?

It gives clear input context (zip code, city, 'City, ST', state name or code, or coordinates) and explicit output-interpretation guidance: show the nearest results even when nothing falls within the 50-mile radius. There are no explicit exclusions or named alternative tools, so the guidance is strong but not complete.

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