Skip to main content
Glama

Get a travel-health doctor

get_provider
Read-onlyIdempotent

The checked details of one verified provider: services, languages, foreign-patient policy, opening hours, date verified, and the HealthPass request link.

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": {
      "slug": "<slug>"
    },
    "name": "get_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile needs no restating. The description adds genuine context beyond that — that the record is 'checked'/verified and carries a 'date verified' freshness marker plus a HealthPass request link — but says nothing about failure modes such as an unknown slug or an unverified provider.

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 tight sentence with no filler, and the most informative part (the returned fields) is listed immediately. The only weakness is that it opens as a noun fragment rather than leading with an action verb, which slightly weakens scannability.

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?

With no output schema in place, the description does a fair job by enumerating the returned fields, which is the main burden for a single-record getter. It is still incomplete on the two things an agent actually needs: how to obtain the slug, and what happens if the slug is invalid or the provider is no longer verified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required 'slug' parameter, and the description never mentions it — it does not explain that the identifier is a slug, where the slug comes from (presumably find_travel_health_provider results), or what format it takes. With one undocumented parameter the description should be compensating, and it is not.

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 names the resource (one verified provider) and enumerates the concrete fields returned: services, languages, foreign-patient policy, opening hours, date verified, HealthPass link. That is far more specific than a restatement of the name, though it is framed as a noun phrase rather than a verb+resource and never explicitly contrasts itself with find_travel_health_provider (list/search) — the singular 'one verified provider' does the differentiation only implicitly.

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

Usage Guidelines2/5

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

There is no when-to-use statement and no mention of the obvious alternative (find_travel_health_provider to locate candidates, prepare_appointment for the next step). The agent must infer that this is the detail-lookup step after a search, and nothing tells it what to do when the desired provider is not verified.

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