Skip to main content
Glama
sepehr071

doctoreto-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Center details

dt_center
Read-onlyIdempotent

Retrieve a medical center's page details—address, departments, services, insurance, hours, lab rules, bookable services, and doctors with earliest free slots—by hash ID or URL.

Instructions

A center's page: address, coordinates, departments, services, accepted insurances, attributes, opening hours, lab admission rules, bookable services with consultation_id (for dt_free_slots) and its doctors (hash ids for dt_doctor, with each doctor's earliest free slot).

Doctor private offices (type office) have no center page: use dt_doctor. Next: dt_free_slots, dt_doctor, dt_reviews(of='center').

Input Schema

NameRequiredDescriptionDefault
centerYesCenter hash id ('YNrrOb') or page URL ('https://doctoreto.com/center/raz-shiraz-lap/YNrrOb').
doctorsNoHow many of its doctors to list (0 = none).
full_textNoReturn complete texts instead of cutting long ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • changedInput schema / properties / center / description
      Previous value: -"Center hash id from a search ('YNrrOb') or its page URL ('https://doctoreto.com/center/raz-shiraz-lap/YNrrOb')."New value: +"Center hash id ('YNrrOb') or page URL ('https://doctoreto.com/center/raz-shiraz-lap/YNrrOb')."
    • removedInput schema / properties / center / title
      Removed value: -"Center"
    • removedInput schema / properties / doctors / title
      Removed value: -"Doctors"
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Return complete texts instead of cutting long ones.",
+  "type": "boolean"
+}
    • removedInput schema / title
      Removed value: -"dt_centerArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dt_centerDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/openWorld/destructive=false, so the safety profile is covered. The description adds substantive behavioral context beyond that: the returned content structure, the consultation_id needed for dt_free_slots, doctor hash ids for dt_doctor, and each doctor's earliest free slot. It does not cover pagination or rate limits, but for a read-only detail endpoint that is minor.

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?

The response content is front-loaded, followed by the exclusion and routing lines, with no filler. It is dense and slightly run-on in the field list, but every clause carries information an agent needs.

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 correctly takes on the burden of describing return content and chaining keys (consultation_id, doctor hash ids), and annotations cover safety. Params are schema-documented. It stops short of explaining vaguer fields like 'attributes' or 'lab admission rules', leaving a small residual gap.

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%, so all three parameters (center, doctors, full_text) are fully documented in the schema with formats and bounds. The description mentions consultation_id and doctor ids, but those are output fields, not parameter guidance, so it adds little beyond the schema. Baseline 3 is appropriate.

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 precisely and enumerates what a center page returns (address, coordinates, departments, services, insurances, opening hours, bookable services, doctors). It also differentiates from the dt_doctor sibling by noting that private offices have no center page. The retrieval verb is only implied by 'A center's page:' rather than stated, which keeps it just under a 5.

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 an explicit exclusion ('Doctor private offices (type office) have no center page: use dt_doctor') and a routing line ('Next: dt_free_slots, dt_doctor, dt_reviews(of=center)'), so the agent knows the alternatives and follow-ups. It does not explicitly position dt_center against dt_search_centers, so the when-to-use is strong but not exhaustive.

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

Deploy Server

Other Tools