Skip to main content
Glama
Sign In

executive-performance

by io.github.degenbmp-25
OverviewDiscussionsAdmin

Get Progress Trend

fitness.get_progress_trend
Read-only

Use this when a user asks how they have been progressing, wants to compare recent assessments, or asks whether something is working. Returns up to five recent pillar scores, overall scores, and the change between them. Do NOT use before the user has completed at least two assessments — there is no trend yet and the honest answer is that one data point is not a trend. Only returns stored derived scores, never raw answers.

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": "fitness.get_progress_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent assessments to include (1-10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds real behavioral context: the tool returns only stored derived scores, never raw answers, and it is meaningless with fewer than two assessments. It stops short of saying how the trend is computed or over what time window, so a 4 rather than a 5.

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?

Three sentences, front-loaded with the use condition, then the return payload, then the exclusion. Nothing is repeated and the negative guidance is placed after the positive so the agent sees the primary trigger first.

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 carries the burden of describing the return, and it does name the payload (pillar scores, overall scores, the change between them). It is nearly complete for a one-parameter read tool, though the description/limit mismatch around five versus ten is a small unresolved gap.

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%, so the limit parameter is already documented by the schema, which sets the baseline at 3. The description says it returns 'up to five' results while the schema allows limit up to 10, leaving a small ambiguity about whether the description's five is a hard cap or just the default, and it adds no guidance on how to choose a limit.

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 states a specific verb and resource ('Returns up to five recent pillar scores, overall scores, and the change between them') and frames the trigger as a question about progress or whether something is working. An agent can tell this is a trend-read tool, distinct from the siblings it would call to build plans or set consent.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use trigger ('user asks how they have been progressing... or asks whether something is working') and an explicit exclusion ('Do NOT use before the user has completed at least two assessments'), including the reason so the agent can explain the refusal. This is the strongest part of the definition.

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

All executive-performance 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