Skip to main content
Glama

Center details

dt_center
Read-onlyIdempotent

Retrieve a medical center's address, departments, services, insurances, hours, lab rules, bookable services, and listed doctors to plan appointments.

Instructions

A center's page: address, departments, services, insurances, hours, lab rules, bookable services with consultation_id (for dt_free_slots) and its doctors (hash ids, earliest free slot).

Doctor private offices have no center page: use dt_doctor. Next: dt_free_slots, dt_doctor.

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": {
      "center": "<center>"
    },
    "name": "dt_center"
  }
}

Input Schema

NameRequiredDescriptionDefault
centerYesCenter hash id ('YNrrOb') or page URL.
doctorsNoDoctors to list (0 = none).
full_textNoReturn full texts, not cut.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • changedInput schema / properties / center / description
      Previous value: -"Center hash id ('YNrrOb') or page URL ('https://doctoreto.com/center/raz-shiraz-lap/YNrrOb')."New value: +"Center hash id ('YNrrOb') or page URL."
    • changedInput schema / properties / doctors / description
      Previous value: -"How many of its doctors to list (0 = none)."New value: +"Doctors to list (0 = none)."
    • changedInput schema / properties / full_text / description
      Previous value: -"Return complete texts instead of cutting long ones."New value: +"Return full texts, not cut."
  2. 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
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds value beyond them by disclosing the cross-tool dependency (consultation_id is the input for dt_free_slots) and that doctor entries carry hash ids and earliest free slot. What it does not clarify is the effect of full_text beyond the schema's own 'not cut' wording.

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 key scoping fact and the alternatives are front-loaded in two short fragments with no filler. The telegraphic, backtick-heavy phrasing and the stray trailing newline make it slightly harder to parse than a clean sentence would be, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only three fully documented parameters, no output schema, and annotations covering the safety profile, the description carries the remaining burden well: it lists the returned fields, explains the key identifier's downstream use, and routes to the correct follow-up tools.

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

Parameters4/5

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

Schema coverage is 100%, so a baseline of 3 is warranted, but the description goes further by explaining what the doctors listing actually contains (hash ids, earliest free slot) and why the bookable-services entries matter (consultation_id feeds dt_free_slots). It does not add anything for the full_text flag beyond the schema.

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?

The description names the resource (a center's page) and enumerates the specific content returned: address, departments, services, insurances, hours, lab rules, bookable services with consultation_id, and doctors. It also explicitly distinguishes itself from dt_doctor for doctor private offices, so an agent can separate the two without opening either schema.

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 when-not ('Doctor private offices have no center page: use dt_doctor') and a downstream routing hint ('Next: dt_free_slots, dt_doctor'), which is strong guidance. The one gap is that it never contrasts with the sibling dt_search_centers, so the search-then-detail flow is only implied.

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