Skip to main content
Glama

Clinic offer details

dt_offer
Read-onlyIdempotent

Fetch one clinic offer's full details, including price, deposit, doctor, place, terms, and bookable variants, using an offer hash ID, numeric ID, or page URL.

Instructions

One clinic offer in full: price, deposit, doctor, place, terms and bookable variants with consultation_id.

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": {
      "offer": "<offer>"
    },
    "name": "dt_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerYesOffer hash id ('ArraJa'), numeric id ('129311') or page URL.
full_textNoReturn full texts, not cut.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / full_text / description
      Previous value: -"Return complete texts instead of cutting long ones."New value: +"Return full texts, not cut."
  2. 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
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value by naming the returned payload fields, but it does not mention behavior for a missing/expired offer, whether the response can be large, or rate/lookup limits that matter for an open-world lookup.

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?

One tight sentence with the core resource front-loaded and no filler. The trailing field list is dense but every item conveys real payload content, so little is wasted.

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 usefully enumerates the expected return fields, and annotations cover the safety profile. For a 2-parameter read lookup this is nearly complete; only the not-found/expired case and the interaction with 'full_text' truncation are unaddressed.

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%, with the 'offer' parameter already documented as accepting a hash id, numeric id, or page URL, and 'full_text' documented as disabling truncation. The description adds nothing about either parameter, so the baseline 3 applies; 'consultation_id' it mentions is a return field, not an input.

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 uses a specific resource ('One clinic offer in full') and enumerates what the response contains (price, deposit, doctor, place, terms, bookable variants with consultation_id). The word 'One' implicitly contrasts with the sibling dt_search_offers, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

There is no explicit when-to-use guidance or exclusion. The phrase 'One clinic offer in full' implies this is the single-record lookup and that dt_search_offers is the discovery path, but the agent must infer that routing from the sibling list rather than from the text.

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