Skip to main content
Glama
sepehr071

doctoreto-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Clinic offer details

dt_offer
Read-onlyIdempotent

Retrieve full details of a clinic offer: price, discount, deposit, provider, location, terms, capacity, expiry, rating, and bookable variants with consultation_id for free slots.

Instructions

One clinic offer in full: price, discount, deposit, who performs it and where, description, terms, capacity, expiry, rating, and bookable variants with consultation_id for dt_free_slots.

Input Schema

NameRequiredDescriptionDefault
offerYesOffer hash id ('ArraJa'), numeric id ('129311') or page URL.
full_textNoReturn complete texts instead of cutting long ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Return complete texts instead of cutting long ones.",
+  "type": "boolean"
+}
    • changedInput schema / properties / offer / description
      Previous value: -"Offer hash id ('ArraJa'), numeric id ('129311') or page URL ('https://doctoreto.com/offer/ArraJa')."New value: +"Offer hash id ('ArraJa'), numeric id ('129311') or page URL."
    • removedInput schema / properties / offer / title
      Removed value: -"Offer"
    • removedInput schema / title
      Removed value: -"dt_offerArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dt_offerDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description adds that long texts are cut by default unless full_text is set, which is useful, but says nothing about auth, rate limits, or error cases for a non-existent offer.

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 front-loaded sentence with zero filler; the only cost is that the long comma-separated field list reads as inventory rather than prioritized information.

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 carries the burden of explaining what comes back, listing the returned fields and variants. It is complete for a read tool, though it omits error behavior for invalid or missing offers.

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%, so both parameters (offer id formats, full_text truncation) are already fully documented in the schema. The description adds no syntax or format detail beyond what the schema provides, 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 resource ('one clinic offer') and scope ('in full'), then enumerates the returned fields, so an agent can distinguish it from dt_search_offers 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 Guidelines3/5

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

Usage is implied by the retrieval framing, and the mention of `consultation_id` for dt_free_slots hints at a follow-up workflow. However, it never states when to call this vs dt_search_offers or dt_center, and gives no exclusions or prerequisites.

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