Skip to main content
Glama

輸入一餐或一天吃的東西

health__check_meal_cancer_risk
Read-onlyIdempotent

[台灣健康資訊]輸入一餐或一天吃的東西(中文),比對 IARC 致癌分級與防癌飲食建議,列出加工肉品、紅肉、酒精、檳榔等風險項目與改善建議。

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": {
      "meal": "<meal>"
    },
    "name": "health__check_meal_cancer_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
mealYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds substantive behavior beyond that: the comparison standard used (IARC classification plus anti-cancer dietary recommendations) and the shape of the response (risk items plus improvement suggestions). It doesn't say whether unmatched or empty input is tolerated.

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 front-loaded sentence with a bracketed jurisdiction tag, and every clause carries information (input language, scope, comparison basis, output contents). No filler, though the trailing list of risk items is somewhat enumerative rather than explanatory.

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 read-only, single-parameter tool with no output schema, the description is close to sufficient: it states the input domain, the knowledge base consulted, and the categories of results. The remaining gap is input formatting guidance, which matters because the parameter is untyped free text.

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

Parameters3/5

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

The single parameter has 0% schema description coverage, so the description carries the burden. It does add meaning — the input should be free-text Chinese naming a single meal or a full day's intake — but gives no format examples, separator conventions, or granularity expectations (e.g. portion sizes).

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 action (compare a meal against IARC carcinogen classifications and anti-cancer dietary guidance) and enumerates the risk categories it reports (processed meat, red meat, alcohol, betel nut). The resource is clearly distinct from sibling health checks, though no sibling is named explicitly.

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 implies use context by saying the input is 'a meal or a day's food, in Chinese,' which tells an agent the acceptable scope of input. It offers no explicit when-not-to-use guidance and no pointer to an alternative tool (e.g. general nutrition or product-safety checks).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources