Skip to main content
Glama
Sign In
cronometer-mcp

cronometer-mcp

by cphoskins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

remove_biometric

Delete a biometric entry in Cronometer by specifying its ID. Find the ID via get_recent_biometrics, then remove outdated or incorrect records.

Instructions

Remove a biometric entry from Cronometer.

Use get_recent_biometrics to find biometric_id values.

Args: biometric_id: The biometric entry ID (e.g. "BXW0DA").

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "biometric_id": "<biometric_id>"
    },
    "name": "remove_biometric"
  }
}

Input Schema

NameRequiredDescriptionDefault
biometric_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It indicates deletion but lacks disclosure on permanence, authorization, or side effects. Adequate for a simple operation.

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 sentences plus an Args section, front-loaded with the main action. Every sentence adds value without redundancy.

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 single-parameter deletion tool with an output schema (present but not described), the description adequately covers core purpose and ID retrieval. Could mention return value but not critical.

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?

Input schema has 0% description coverage, but description adds an example format ('e.g. BXW0DA'), which compensates and clarifies the expected string format.

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 clearly states 'Remove a biometric entry from Cronometer', using a specific verb and resource. It distinguishes from sibling tools like add_biometric.

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?

Explicitly guides the agent to use get_recent_biometrics to find the biometric_id. Does not mention when not to use or alternatives, but provides necessary context for ID retrieval.

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