Skip to main content
Glama

MedaRep

Find surgeons, practices and places

search
Read-onlyIdempotent

Search by name. Returns surgeons (npi), practices (pacId), hospitals and ASCs (ccn), device companies (company slug), states, metros (metro code) and counties (FIPS), for use in the other tools.

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

Input Schema

NameRequiredDescriptionDefault
queryYesA name or part of one: surgeon, practice, city, county, metro or state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds value by disclosing the shape of results (typed entities with their ID systems), but says nothing about result limits, ordering/ranking, or how ambiguous partial-name matches are resolved.

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 sentences, front-loaded with the core action and then the payoff (returned types and IDs). Every clause carries information an agent needs to chain the result into other tools.

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?

With no output schema, the description carries the burden of describing return values and does so well by listing entity types and identifier formats. Remaining gaps — pagination, ranking, and disambiguation of partial matches — are modest for a single-parameter search tool.

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 the single parameter's own description already spells out that it accepts a name or partial name for surgeon, practice, city, county, metro or state. The description's 'Search by name' adds no syntax, matching, or case-sensitivity detail beyond that, so the 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 verb (search) and enumerates exactly which resource types are returned — surgeons, practices, hospitals/ASCs, device companies, states, metros, counties — each with its identifier form (npi, pacId, ccn, slug, metro code, FIPS). This makes it unmistakably the lookup/resolution tool rather than one of the profile or list siblings.

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?

The phrase 'for use in the other tools' tells the agent this is a resolution step whose purpose is to obtain IDs for downstream calls, which is clear positioning. It stops short of explicit when-not guidance or naming a specific alternative when the agent already knows the ID.

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