Skip to main content
Glama

Little Works

find_doctors

Find doctors / clinicians via Discover search + hire landings for a place; then Book or Message.

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_doctors"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoe.g. victoria-bc
specialtyNodoctor|family-doctor|physician|…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavioral traits beyond the schema: that results are aggregated from two distinct sources and that the outcome flow can lead to booking or messaging. However, it says nothing about read-only safety, permissions, result shape, or pagination.

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?

A single front-loaded sentence with essentially no wasted words; the source mechanisms are stated immediately. The compressed notation ("+ hire landings") and the appended "then Book or Message" trade a little clarity for brevity.

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?

For a simple two-parameter read tool with no output schema, the definition covers what the tool does and where results come from, but omits what an agent will actually receive (doctor listings, profiles, availability?) and whether results are bounded, which matters for planning follow-up calls.

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% with only two optional parameters, so the schema already documents both. The phrase "for a place" reinforces the place parameter's role as a scope filter but adds no syntax or value guidance beyond what the schema supplies, so the baseline of 3 applies.

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?

"Find doctors / clinicians" gives a specific verb and resource, and the description adds that results come from two sources (Discover search and hire landings). It is slightly blurred by the trailing "then Book or Message," which mixes retrieval with follow-on actions and leaves it unclear whether this tool itself initiates booking or messaging.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"via Discover search + hire landings for a place" implies the context of use (location-scoped practitioner lookup), but there is no explicit when-to-use versus when-not, and it never states how it relates to the existing discover_search sibling beyond naming it as a data source.

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