Skip to main content
Glama

KinToolkit: Medicine Dosage Calculator Label References for Children and Infants

List medicine question guides

list_question_guides

Discover every published educational question guide, including symptoms, timing, food, bottle comparisons, label charts, Zyrtec chewables and Claritin. Returns public guide_id values, descriptions, update dates and canonical HTML/Markdown links. Use get_question_guide for complete content. No search text or patient inputs. Operational telemetry excludes arguments and results.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
scopeYes
guidesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / guides / items / properties / guide_id / enum
      Previous value: -[
      -  "cetirizine-zyrtec-babies-under-2",
      -  "infant-tylenol-under-2-years",
      -  "infant-motrin-6-to-23-months",
      -  "tylenol-motrin-24-to-35-lb",
      -  "medicine-dose-pounds-kilograms",
      -  "childrens-zyrtec-liquid-chewable-dissolve-tabs",
      -  "childrens-zyrtec-2-5-mg-chewable-label",
      -  "childrens-claritin-liquid-label",
      -  "childrens-cetirizine-mg-per-kg",
      -  "infant-motrin-under-6-months",
      -  "medicine-bottle-online-chart-disagree",
      -  "childrens-zyrtec-dose-age-or-weight",
      -  "infant-vs-childrens-motrin-concentration",
      -  "infant-vs-childrens-tylenol",
      -  "childrens-motrin-30-lb",
      -  "childrens-zyrtec-2-year-old",
      -  "childrens-zyrtec-10-month-old",
      -  "childrens-tylenol-weight-or-age",
      -  "tylenol-160-mg-per-5-ml-meaning",
      -  "child-age-weight-different-dose-chart-rows",
      -  "measure-childrens-liquid-medicine"
      -]New value: +[
      +  "cetirizine-zyrtec-babies-under-2",
      +  "infant-tylenol-under-2-years",
      +  "infant-motrin-6-to-23-months",
      +  "tylenol-motrin-24-to-35-lb",
      +  "medicine-dose-pounds-kilograms",
      +  "childrens-zyrtec-liquid-chewable-dissolve-tabs",
      +  "childrens-zyrtec-2-5-mg-chewable-label",
      +  "childrens-claritin-liquid-label",
      +  "childrens-cetirizine-mg-per-kg",
      +  "infant-motrin-under-6-months",
      +  "medicine-bottle-online-chart-disagree",
      +  "childrens-zyrtec-dose-age-or-weight",
      +  "infant-vs-childrens-motrin-concentration",
      +  "infant-vs-childrens-tylenol",
      +  "childrens-motrin-30-lb",
      +  "childrens-zyrtec-2-year-old",
      +  "childrens-zyrtec-10-month-old",
      +  "childrens-tylenol-weight-or-age",
      +  "tylenol-160-mg-per-5-ml-meaning",
      +  "child-age-weight-different-dose-chart-rows",
      +  "measure-childrens-liquid-medicine",
      +  "what-childrens-zyrtec-claritin-help-with",
      +  "zyrtec-claritin-child-cough-stuffy-nose",
      +  "childrens-zyrtec-claritin-morning-or-night",
      +  "childrens-allergy-medicine-with-food",
      +  "childrens-allergy-medicine-every-day",
      +  "child-fever-acting-normal-medicine",
      +  "tylenol-motrin-cough-cold-symptoms",
      +  "child-sore-throat-tylenol-motrin",
      +  "wake-sleeping-child-fever-medicine",
      +  "childrens-medicine-with-food",
      +  "tylenol-motrin-how-often-how-many-days"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / guides / items / properties / guide_id / enum
      Previous value: -[
      -  "childrens-zyrtec-liquid-chewable-dissolve-tabs",
      -  "childrens-zyrtec-2-5-mg-chewable-label",
      -  "childrens-claritin-liquid-label",
      -  "childrens-cetirizine-mg-per-kg",
      -  "infant-motrin-under-6-months",
      -  "medicine-bottle-online-chart-disagree",
      -  "childrens-zyrtec-dose-age-or-weight",
      -  "infant-vs-childrens-motrin-concentration",
      -  "infant-vs-childrens-tylenol",
      -  "childrens-motrin-30-lb",
      -  "childrens-zyrtec-2-year-old",
      -  "childrens-zyrtec-10-month-old",
      -  "childrens-tylenol-weight-or-age",
      -  "tylenol-160-mg-per-5-ml-meaning",
      -  "child-age-weight-different-dose-chart-rows",
      -  "measure-childrens-liquid-medicine"
      -]New value: +[
      +  "cetirizine-zyrtec-babies-under-2",
      +  "infant-tylenol-under-2-years",
      +  "infant-motrin-6-to-23-months",
      +  "tylenol-motrin-24-to-35-lb",
      +  "medicine-dose-pounds-kilograms",
      +  "childrens-zyrtec-liquid-chewable-dissolve-tabs",
      +  "childrens-zyrtec-2-5-mg-chewable-label",
      +  "childrens-claritin-liquid-label",
      +  "childrens-cetirizine-mg-per-kg",
      +  "infant-motrin-under-6-months",
      +  "medicine-bottle-online-chart-disagree",
      +  "childrens-zyrtec-dose-age-or-weight",
      +  "infant-vs-childrens-motrin-concentration",
      +  "infant-vs-childrens-tylenol",
      +  "childrens-motrin-30-lb",
      +  "childrens-zyrtec-2-year-old",
      +  "childrens-zyrtec-10-month-old",
      +  "childrens-tylenol-weight-or-age",
      +  "tylenol-160-mg-per-5-ml-meaning",
      +  "child-age-weight-different-dose-chart-rows",
      +  "measure-childrens-liquid-medicine"
      +]
  3. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations are present but oddly set (readOnlyHint=false and idempotentHint=false for a parameterless list operation), and the description never reconciles that. It does add useful context beyond the annotations: what fields come back, that no inputs are accepted, and that telemetry excludes arguments/results. No contradiction is stated outright, but the gap between 'list' semantics and the annotations is left unexplained.

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?

Front-loaded with the action and scope, then returns, then the sibling redirect. Slightly padded by the topical example list ('symptoms, timing, food, bottle comparisons, label charts, Zyrtec chewables and Claritin'), which conveys coverage but reads as promotional rather than functional.

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?

For a parameterless list tool with an output schema, the description covers purpose, return fields, the sibling alternative, and the absence of inputs. An agent has everything needed to select and call it 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?

Zero parameters, so the baseline is 4. The description reinforces this by explicitly saying 'No search text or patient inputs', preempting an agent from trying to pass a query argument despite additionalProperties=false.

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?

Specific verb+resource ('Discover every published educational question guide') with the returned fields named (guide_id, descriptions, update dates, HTML/Markdown links). It distinguishes itself from the sibling get_question_guide by scope: this lists, the sibling returns complete content.

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?

Explicitly routes the agent to get_question_guide for full content and states 'No search text or patient inputs', telling the caller this cannot be used for filtering/search. It stops short of describing the situational trigger (e.g., browse to pick an ID before fetching), so it is clear context rather than full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources