Skip to main content
Glama
xunji-private-mcp

xunji-private-mcp

by Vdk1639

search_official_food

Read-only

Search Xunji's official foods by keyword to retrieve per-100g nutrition, IDs, unique keys, and units for accurate diet records.

Instructions

Search Xunji's official foods. Prefer foods over the compact d array in the result.

Each d row is [id, name, cal, carb, fat, protein, foodpic, uniquekey, units]. Nutrition values are per 100 g. Preserve uniquekey, ntr and units when recording a match.

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": {
      "keyword": "<keyword>"
    },
    "name": "search_official_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description adds real value on top: the response carries both a `foods` collection and a compact `d` array, each `d` row has a fixed 9-field layout, values are per 100 g, and uniquekey/ntr/units must be preserved when recording a match. The only gap is that `ntr` is referenced but never explained.

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, front-loaded sentences: purpose first, then result-shape guidance, then the row layout. Every sentence carries information, though the ordering is slightly awkward since it recommends `foods` before explaining what `d` is.

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

Completeness3/5

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

With no output schema, the description correctly takes on the burden of explaining the return shape and the per-100 g convention, which is genuinely needed. It is still incomplete for a two-parameter search tool: no mention of the limit default, matching behavior (partial name vs exact), or ordering.

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 it largely does not. `keyword` is only implied by "search", and `limit` (default 8, minimum 1) is never mentioned, leaving result-count behavior undocumented.

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?

"Search Xunji's official foods" names a specific verb (search) and resource (official food catalog), which distinguishes it from record-query siblings like query_food_records. It stops short of naming or contrasting any sibling explicitly, so an agent must infer the boundary itself.

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 statement of when to use this versus query_food_records or upsert_custom_food, and no prerequisites. The only guidance ("prefer foods over the compact d array") concerns post-retrieval handling of results, not tool selection.

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