Skip to main content
Glama
Sign In
HealthLedger MCP

HealthLedger MCP

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

List tracked metrics

list_metrics
Read-onlyIdempotent

Retrieve all health metrics recorded for a user, showing data counts and the most recent value for each metric.

Instructions

List which metrics have data for a user, with counts and the latest value of each.

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_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds context about returning counts and latest values. No contradictions, but does not disclose behavior for null 'user' parameter.

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, front-loaded sentence with no wasted words. Efficiently conveys core functionality.

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?

Given simple input, presence of output schema, and low complexity, the description is mostly sufficient. Could elaborate on the scope of metrics, but the output schema fills in details.

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 coverage is 0%, but description partially compensates by stating the output is 'for a user'. However, it does not explain the meaning of null default or provide format details beyond the schema.

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 metrics with data for a user, including counts and latest values. It distinguishes from sibling 'get_metrics' by implying it returns only metrics that have data, but does not explicitly differentiate.

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 'get_metrics' or other list tools. No mention of prerequisites or when not to use.

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