Skip to main content
Glama
Sign In
doctoreto-mcp

doctoreto-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Health articles

dt_health_articles
Read-onlyIdempotent

Search Doctoreto's health magazine for background on conditions, tests, or treatments; get titles, links, dates, and summaries, and set text_chars to read article text.

Instructions

Search Doctoreto's health magazine (about 5,000 articles) for background on a condition, test or treatment.

Returns title, link, publish date and a summary; set text_chars to read the articles. General information only, not medical advice: for a diagnosis book a doctor (dt_search_doctors).

Input Schema

NameRequiredDescriptionDefault
limitNoMax articles.
queryYesDisease, test, drug or treatment in Persian, e.g. 'فشار خون' or 'آزمایش تیروئید'.
text_charsNoCharacters of article text to include per article; 0 = summary only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / text_chars / title
      Removed value: -"Text Chars"
    • removedInput schema / title
      Removed value: -"dt_health_articlesArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dt_health_articlesDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description only needs to add context. It does: it discloses the returned fields (title, link, publish date, summary) and the cost/behavior switch that text_chars controls. No auth, rate-limit, or ordering details are given, which keeps it from a 5.

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

Conciseness5/5

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

Two short sentences plus a routing caveat; the purpose and corpus size are front-loaded, and every clause (returned fields, text_chars behavior, the not-medical-advice boundary) earns its place.

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 no output schema, the description correctly compensates by listing the return fields and explaining the summary-vs-full-text behavior. Combined with a 100%-covered input schema and rich annotations, an agent has everything needed to call this tool correctly.

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 the baseline is 3, but the description adds practical meaning beyond the schema by explaining that setting text_chars is how you actually 'read the articles' rather than just naming it. limit and query are left entirely to the schema, which documents them well.

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 verb and resource ('Search Doctoreto's health magazine') with scale context (~5,000 articles) and the intended subject matter (condition, test, treatment). It is clearly distinguishable from sibling tools like dt_search_doctors and dt_reviews.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use ('for background on a condition, test or treatment') and when-not ('General information only, not medical advice: for a diagnosis book a doctor'), naming the alternative tool dt_search_doctors. Nothing is left to inference.

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