Skip to main content
Glama
xunji-private-mcp

xunji-private-mcp

by Vdk1639

query_body_metrics

Read-only

Read personal Xunji body metric records for a date range, filter by metric types, and paginate results with limit and offset.

Instructions

Read personal Xunji body metric records. Omit types to include all metrics.

Use the wire name weist for waist circumference. Use limit and offset to paginate records.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "query_body_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
typesNo
offsetNo
end_dateYes
start_dateYes
include_latestNo
include_recordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description only needs to add context. It contributes the wire-name quirk and pagination behavior, but says nothing about what include_latest and include_records (both defaulting true) do to the response, which is the main behavioral unknown for a 7-parameter read.

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?

Three short sentences, front-loaded with the purpose and then the two operational notes, with no filler. It is tightly written, though the paragraph break mid-thought slightly fragments the guidance.

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

Completeness2/5

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

For a 7-parameter tool with no output schema and zero schema description coverage, the definition should explain the response-shaping flags and the date range semantics. It omits include_latest and include_records entirely and never clarifies whether the date range is inclusive or how the result set is bounded by the 500 default limit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, yet it only explains types, limit, and offset. The two required date parameters are self-evident from their names and date format, but include_latest and include_records are undocumented in both schema and description, leaving 2-3 meaningful parameters with no semantics at all.

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?

"Read personal Xunji body metric records" gives a specific verb plus resource, and the read framing implicitly separates it from the sibling upsert_body_metrics write path. It does not explicitly name a sibling alternative, so it stops short of a 5.

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?

The description gives operational guidance for two parameters (omit types to get all metrics; use limit/offset to paginate), which implies the common usage pattern. It never states when this tool should be chosen over query_food_records or get_training, nor any prerequisite or exclusion, so guidance remains implied rather than explicit.

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