Skip to main content
Glama
Sign In
HealthLedger MCP

HealthLedger MCP

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

List substance use logs

list_substance_use_logs
Read-onlyIdempotent

Retrieve substance-use logs filtered by substance, date range, or user to monitor health records.

Instructions

List substance-use logs, optionally filtered by substance/date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_substance_use_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo
limitNo
sinceNo
untilNo
substanceNo

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 indicate readOnlyHint and idempotentHint, so the description's 'list' action is consistent but adds no new behavioral details beyond the annotations. It doesn't discuss pagination, ordering, or rate limits.

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, no wasted words. Front-loaded with action and resource.

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

Completeness3/5

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

Given the parameter count (5, none required) and the existence of an output schema, the description is minimally adequate but lacks details on the user filter, limit behavior, and date format. Could be improved for better completeness.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must add meaning. It briefly hints at substance and date filtering but does not explain all parameters (user, limit) or provide syntax/format for the date strings. This is insufficient for a 5-parameter tool.

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 clearly states the tool lists substance-use logs with optional filtering by substance or date. It distinguishes from sibling list tools by the specific resource, though it could be more explicit about the difference from other list tools.

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 like search_records or semantic_search. No mention of prerequisites or when not to use it.

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