Skip to main content
Glama
Sign In
HealthLedger MCP

HealthLedger MCP

by Cole-Will-I-Am
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Analyze substance trend

analyze_substance_trend
Read-onlyIdempotent

Retrieve daily total stats for a specific substance from health records, providing analysis-ready numeric trends over a date range.

Instructions

Return descriptive daily-total stats for one substance when numeric amounts exist.

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": {
      "substance": "<substance>"
    },
    "name": "analyze_substance_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo
sinceNo
untilNo
substanceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds the condition 'when numeric amounts exist' but lacks detail on edge cases (e.g., no data, multiple logs per day) or aggregation behavior.

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?

Single sentence of 12 words. Front-loaded with the core action ('Return descriptive daily-total stats'). No redundant information.

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

Completeness2/5

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

Despite having an output schema, the description omits crucial context: parameter details, return value specifics, and when to use. Leaves significant gaps for a 4-parameter tool.

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

Parameters1/5

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

With 0% schema description coverage, the description must compensate but only mentions 'substance' implicitly. No explanation for user, since, until parameters (optional, date formats, filtering behavior).

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 clearly states the verb ('Return'), resource ('daily-total stats for one substance'), and a condition ('when numeric amounts exist'). It distinguishes from sibling tools like analyze_biomarker_trend by specifying 'substance'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., analyze_trend, analyze_biomarker_trend). The description does not state 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