Skip to main content
Glama
Sign In
health-mcp

health-mcp

by ojimpo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_current_status

Retrieve current health dashboard snapshot: overall status, cultural activity scores, per-category cards, condition states, and trend comments. Use for 'how am I doing' queries.

Instructions

Get the current snapshot of the personal health dashboard (health.ojimpo.com): overall health score/status (NORMAL/CAUTION/CRITICAL) and cultural activity score/status (RICH/MODERATE/LOW), per-category cards (this week vs previous week with change), condition state cards (sleep/readiness/stress/weight/outing/CTL), and trend comments. Scores are percentages of personal baselines (100 = baseline met). Use this first for any 'how am I doing' question.

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": "get_current_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It describes the tool as a 'snapshot' implying a read operation without side effects, but it does not explicitly state read-only, auth requirements, or rate limits. The description adds context about scores being percentages of baselines but lacks full transparency on behavior.

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?

The description is one long sentence but front-loaded with the core purpose and efficiently lists the returned elements. It is fairly concise with no wasted words, though it could be broken into multiple sentences for readability.

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?

With no output schema, the description adequately describes the return structure: overall scores, per-category cards, condition state cards, and trend comments. It also explains score interpretation (percentages of baselines). The usage guidance adds completeness. Minor gaps: does not detail card structure or trend comment format.

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?

There are no parameters, and the schema coverage is trivially 100%. Per guidelines, baseline is 4. The description does not need to add parameter details since there are none.

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 it retrieves the current snapshot of the health dashboard, listing specific components like overall health status, cultural activity score, per-category cards, condition state cards, and trend comments. It distinguishes from siblings like get_recent_activities (activities), get_score_history (history), and query_records (general query).

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?

The description explicitly advises to use this tool first for any 'how am I doing' question, providing strong usage guidance. It does not list exclusions or alternative tools for specific cases, but the context makes it clear this is the primary status tool.

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