Skip to main content
Glama
fitdays-mcp-server

fitdays-mcp-server

by brad28820

Refresh sync cache

refresh_sync

Force-refreshes the global FitDays cache and returns synchronized counts for devices, users, height records, and weight records, including active, deleted, and total totals.

Instructions

Force-refresh the global FitDays cache shared by all tools. FitDays data is loaded lazily: the first tool call that needs synchronized account data fetches a fresh snapshot and stores it in the global cache for 5 minutes. Returns synchronized record counts for devices, users, height_records, and weight_records (active, deleted, total).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: it discloses that the cache is global and shared by all tools, that loading is lazy, the 5-minute TTL, and the exact shape of the return payload. It omits cost/latency of a forced refresh and failure behavior, which keeps it below the top mark for a no-annotation tool.

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 compact sentences ordered by importance: what the action is, why the cache exists, then what comes back. Every sentence adds information and none restates the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema, the definition supplies both the side effect (global cache refresh) and the return shape (counts for devices, users, height_records, weight_records with active/deleted/total). An agent has everything it needs to decide and to interpret the result.

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?

The tool takes zero parameters and the schema is a bare object, so there is no parameter semantics to explain; baseline 4 applies. The description correctly avoids inventing parameters.

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?

States a specific verb and resource ("Force-refresh the global FitDays cache") and scopes it as global across all tools. No sibling in the list (get_latest_weight, list_users, etc.) performs a refresh, so there is no ambiguity to resolve — the action is unmistakable.

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 lazy-loading and 5-minute TTL explanation gives a clear context for when a manual refresh is warranted (data older than the cache window). It stops short of explicitly saying "call this when you need data fresher than 5 minutes" or naming when not to call it, so it is strong context rather than a full when/when-not rule.

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