Skip to main content
Glama
xunji-private-mcp

xunji-private-mcp

by Vdk1639

query_food_records

Read-only

Retrieve Xunji food records for an inclusive date range, including optional details, to review dietary intake over a chosen period.

Instructions

Read the requested inclusive date range of Xunji food 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_food_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes
include_detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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. The description adds one genuinely useful behavioral fact beyond the schema: the date range is inclusive on both boundaries. It says nothing about ordering, volume, pagination, or what the Xunji source implies for data availability.

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?

A single sentence with no filler, and the scope constraint is front-loaded. It is tight rather than padded, though the brevity comes partly from omitting information the agent needs.

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?

With zero schema description coverage and no output schema, the description bears the full burden of explaining the three parameters and the shape of the return. It covers the date range only, leaving include_detail and the response contents undocumented for a tool whose output an agent must interpret.

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 must carry parameter meaning and mostly does not. 'Inclusive date range' usefully pins down start_date/end_date boundary semantics, but include_detail (default true) is left entirely unexplained, leaving a third of the parameters undocumented in both structured and unstructured text.

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 ('Read') and resource ('Xunji food records'), scoped to a date range, which implicitly separates it from the write-side sibling upsert_food_records. No sibling is named explicitly, so an agent must infer the read/write split from the name alone.

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 when-to-use guidance, no prerequisites, and no exclusion or alternative named. The only hint is the word 'requested', which implies the caller already knows the range, but nothing tells the agent when this query is preferable to query_body_metrics or search_official_food.

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