Skip to main content
Glama

add_weigh_in_with_timestamps

Records a new weight measurement with optional local and GMT timestamps, using current time by default or deriving GMT from the local date when only one is provided.

Instructions

Add a new weight measurement with specific timestamps

    If both timestamps are omitted, the current time is used. If only
    date_timestamp is given, the GMT timestamp is derived from it.

    Args:
        weight: Weight value
        unit_key: Unit of weight ('kg' or 'lbs'; 'lb' is accepted as an alias)
        date_timestamp: Local timestamp in format YYYY-MM-DDThh:mm:ss
            (required if gmt_timestamp is given -- it sets the day the
            weigh-in is recorded on)
        gmt_timestamp: GMT timestamp in format YYYY-MM-DDThh:mm:ss
    

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": {
      "weight": "<weight>"
    },
    "name": "add_weigh_in_with_timestamps"
  }
}

Input Schema

NameRequiredDescriptionDefault
weightYes
unit_keyNokg
gmt_timestampNo
date_timestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world write, so the safety profile is covered. The description adds real behavioral detail beyond that: default timestamping to now, derivation of GMT from the local date, the cross-field requirement that date_timestamp be present when gmt_timestamp is given, and the 'lb' alias. It stops short of saying what happens if a weigh-in already exists for that day or what errors to expect.

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 purpose sentence is front-loaded and the rest is compact, with each clause carrying real information. The raw docstring 'Args:' block and mid-sentence line breaks weaken readability somewhat, but no sentence is wasted.

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 four-parameter write tool with no output schema and no annotation-level detail on side effects, the definition covers defaults, required-parameter conditions, and timestamp formats adequately. The remaining gap is the write's effect on existing data (overwrite vs. append) and what the call returns.

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 description coverage is 0%, so the description must carry the parameter burden, and it largely does: it explains weight, unit_key (with the 'lb' alias), and both timestamps including the exact 'YYYY-MM-DDThh:mm:ss' format and their conditional relationship. It slightly under-specifies weight ranges/units per unit_key and does not restate the default of 'kg', which keeps it off a 5.

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?

States a specific verb and resource ("Add a new weight measurement") plus a distinguishing qualifier ("with specific timestamps"). That qualifier implicitly separates it from the plain add_weigh_in sibling, but the description never names that alternative, so a reader must infer the boundary from the title alone.

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?

Gives conditional guidance about omitting or partially supplying timestamps (current time used, GMT derived from date_timestamp), which shapes how the tool is invoked. However, there is no explicit statement of when to prefer this tool over add_weigh_in, or any exclusion conditions, so the when-not guidance is absent.

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