Skip to main content
Glama
Sign In

FindADoctor.si

by si.findadoctor.api
OverviewDiscussionsAdmin

About database

about_database
Read-onlyIdempotent

What one country's database holds: sources, dates, counts and coverage. Set country: United States (country=US), New Zealand (country=NZ), France (country=FR).

United States (country=US): Sources, build date, coverage counts, scoring method and caveats.

New Zealand (country=NZ): Sources, read dates, coverage counts and known gaps. Free.

France (country=FR): Sources, licences, read dates, coverage counts and known gaps. Free.

Input Schema

NameRequiredDescriptionDefault
countryYesWhere the person wants to be seen: United States (country=US), New Zealand (country=NZ), France (country=FR). Decide it before searching; if unclear, ask the person. Older clients that leave it out get United States.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Where the person wants to be seen: United States (country=US), New Zealand (country=NZ). Decide it before searching; if unclear, ask the person. Older clients that leave it out get United States."New value: +"Where the person wants to be seen: United States (country=US), New Zealand (country=NZ), France (country=FR). Decide it before searching; if unclear, ask the person. Older clients that leave it out get United States."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "US",
-  "NZ"
-]New value: +[
+  "US",
+  "NZ",
+  "FR"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Where the person wants to be seen: United States (country=US), New Zealand (country=NZ). Decide it before searching; if unclear, ask the person. Older clients that leave it out get United States.",
+  "enum": [
+    "US",
+    "NZ"
+  ],
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "country"
+]
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds useful context on what each country's dataset yields and the notable 'Free' designation for NZ/FR, but says nothing about response shape, size, or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the country enum mapping is repeated (once in the intro, again in the per-country lines, and a third time in the schema) and the per-country lines are near-duplicates of each other, diluting the value.

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 single-parameter, 100%-covered tool with no output schema, the description usefully outlines what the call returns (sources, dates, counts, coverage, gaps) and flags per-country availability, which is sufficient for an agent to decide to invoke it.

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% and the country enum is fully documented in the schema, so the baseline is 3. The description merely restates the same US/NZ/FR mapping already present in the schema, adding no new meaning such as default behavior or format expectations.

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 opening sentence names a specific resource and enumerates what the database metadata contains (sources, dates, counts, coverage), which is far more concrete than the tautological title 'About database'. It is clearly distinct from the search/list siblings, though it never explicitly says so.

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 statement of when to call this versus lookup_terms or the other metadata-adjacent siblings, and no exclusions or prerequisites. The per-country lines describe data content, not call conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FindADoctor.si toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources