Skip to main content
Glama
xunji-private-mcp

xunji-private-mcp

by Vdk1639

upsert_body_metrics

DestructiveIdempotent

Preview and confirm adding or updating body metrics by date and type, using kg for weight, % for bodyfat, and cm for circumference or size.

Instructions

Preview and confirm adding or updating body metrics by date and type.

Use kg for weight, % for bodyfat, and cm for circumference or size. Reuse client_request_id if retrying the same request after an uncertain result.

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": {
      "records": "<records>"
    },
    "name": "upsert_body_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordsYes
client_request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructive, idempotent, and open-world behavior, so the bar is lower; the description still adds substance by disclosing a two-phase preview/confirm flow and how idempotency is achieved via client_request_id. It does not say what happens to an existing value when a record for the same date and type is overwritten, which is the main remaining behavioral gap.

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 short sentences, each carrying distinct information, with the core action stated first and the unit and idempotency details following. No filler or restatement of the 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 two-parameter mutation tool with no output schema and no schema descriptions, the definition covers the essentials: what it mutates, units, and retry behavior. The one unresolved point is how confirmation is expressed, since no confirm parameter exists in the schema, which leaves the second half of the advertised workflow ambiguous.

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 weight, and it does add meaning the schema lacks: the unit for 'value' varies by type (kg for weight, % for bodyfat, cm for circumference/size), and client_request_id is given explicit retry semantics. It says nothing about the records array shape or the datestr format, but those are largely self-evident from the schema.

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?

The description names a specific verb and resource: adding or updating body metrics, qualified by date and type, with a preview-then-confirm framing. This is clearly distinguishable from query_body_metrics, though that alternative is never named.

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?

It gives concrete retry guidance (reuse client_request_id after an uncertain result) and unit conventions, which is real usage help. However, it never states when to prefer this over the read-only sibling, nor does it explain the conditions or mechanism for the 'confirm' step.

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