Skip to main content
Glama
Sign In
COLMI Smart Ring MCP Server

COLMI Smart Ring MCP Server

by orviwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_daily_activity

Retrieve daily step count, estimated calories burned, and distance walked from a COLMI smart ring for today or prior days to track activity.

Instructions

Queries the smart ring for step count, estimated calories burned, and distance walked. days_ago: 0 for today, 1 for yesterday, etc.

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

Input Schema

NameRequiredDescriptionDefault
addressNo
days_agoNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'Queries' implies a read-only operation and the metric list implies the payload, but there is no mention of authentication, rate limits, caching, or how historical data availability is bounded on the ring.

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 lines, both load-bearing, with the core capability front-loaded and the only parameter convention on its own line. No filler or restatement of the tool name.

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, zero-required-parameter tool with an output schema already covering return values, the description is nearly sufficient. The one substantive hole is the undocumented address parameter and the absence of any note about how far back data is retained.

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 description coverage is 0%, so the description must compensate. It does explain days_ago (0 = today, 1 = yesterday), adding real meaning beyond the schema's bare default, but the address parameter is left completely undocumented in both schema and description, leaving half the inputs ambiguous.

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 (Queries) plus the resource (smart ring) and enumerates the exact metrics returned: step count, calories burned, distance walked. This cleanly separates it from siblings like get_sleep_and_recovery, read_realtime_vitals, and get_motion_sample without opening any schema.

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

Usage Guidelines2/5

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

There is no guidance on when to prefer this over read_realtime_vitals or get_motion_sample, nor any prerequisites or exclusions. The only usage-ish content is the days_ago convention, which is parameter semantics rather than tool selection guidance.

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