Skip to main content
Glama
Sign In
health-mcp

health-mcp

by ojimpo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_recent_activities

Retrieve recent activities from all sources (music, workouts, movies, commits) as human-readable lines with relative time.

Instructions

List the most recent concrete activities across all sources (e.g. tracks listened, workouts, movies watched, commits) as human-readable lines with relative time. The backend keeps the latest 8.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax items (default 8).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Description reveals it returns human-readable lines with relative time and a backend limit of 8, but lacks disclosure on side effects given no annotations. Adequate for listed 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?

Two concise sentences front-load the main functionality and include important details without unnecessary text.

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?

For a simple list tool with one parameter and no output schema, the description adequately covers functionality and constraints.

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

Parameters3/5

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

Schema coverage is 100%; the description mentions 'latest 8' which aligns with the parameter's default and max, adding no new meaning beyond schema.

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?

Clearly states it lists recent activities across multiple sources with human-readable lines and relative time, distinguishing it from siblings like get_current_status or query_records.

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

Usage Guidelines3/5

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

Implies usage for retrieving recent activities, but does not explicitly specify when to use vs alternatives or provide exclusions.

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