Skip to main content
Glama
Sign In

GlucoBeat

by com.glucobeat
OverviewDiscussionsAdmin

Resumen del ejercicio

get_exercise_summary
Read-onlyIdempotent

Días con ejercicio frente a días sin él en un periodo (por defecto, los últimos 30 días; hasta 180), y por tipo de actividad: cambio durante las sesiones y bajadas en las 24 h siguientes. Siempre es una consulta completa.

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

Input Schema

NameRequiredDescriptionDefault
toNoLocal date 'YYYY-MM-DD' or ISO 8601 date-time.
fromNoLocal date 'YYYY-MM-DD' or ISO 8601 date-time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare a safe, idempotent, read-only operation, and the description adds meaningful behavior beyond them: default 30-day window, 180-day cap, complete-query semantics, and the specific exercise effects reported. It does not clarify pagination or exact response shape, but that is a minor gap for this simple read tool.

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 definition is a single compact sentence that front-loads the main comparison and then adds period and metric details. The final clause 'Siempre es una consulta completa' is somewhat vague, but the description is not verbose.

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 two-optional-parameter read tool with full schema coverage and no output schema, the description covers what is summarized, the default and maximum periods, and the included activity-type metrics. It is largely complete, though return formatting remains unspecified.

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?

Schema coverage is 100% and both from/to are documented in the schema, so the baseline would be 3. The description adds temporal meaning by stating the default last-30-days behavior and the 180-day maximum, though it does not specify inclusive/exclusive bounds or behavior when only one date is supplied.

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 names a specific resource and comparison: days with exercise versus days without over a period, broken down by activity type and two exercise-related metrics. It does not explicitly distinguish this from summary siblings such as get_stats, so it falls short of full sibling differentiation.

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?

It provides useful invocation context: the default period is the last 30 days and the maximum is 180 days, and it states the query is always complete. However, it gives no explicit when-to-use guidance or alternatives to sibling tools like get_stats.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GlucoBeat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources