Skip to main content
Glama

輸入一餐或一天吃的東西

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": "check_meal_cancer_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
mealYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real behavioral value beyond that by disclosing the comparison basis (IARC grading plus dietary guidelines) and the shape of the response: risk items and improvement suggestions. It does not flag limitations such as one-meal-vs-one-day granularity effects or whether the output is general guidance rather than medical advice.

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?

A single front-loaded sentence packs the input, the comparison method, the enumerated risk categories, and the output type with no redundant wording. Nothing could be removed without losing information.

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?

With no output schema, the description must convey what comes back, and it does (risk items plus improvement suggestions). Combined with rich read-only annotations and a single free-text parameter, this is nearly complete; the only gap is no guidance on input language fallback or scope limits.

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% — the single 'meal' string parameter is entirely undocumented in the schema. The description compensates by specifying the content (food eaten in one meal or one day) and the required language (Chinese), which is genuinely useful input-formatting guidance beyond 'meal: string'. It still leaves the expected level of detail or structure of the free-text input unspecified.

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 states a concrete action chain: input a meal or a day of food, compare it against IARC carcinogen classifications and cancer-prevention dietary guidelines, and list risk items (processed meat, red meat, alcohol, betel nut) with improvement suggestions. That is a specific verb+resource with a visible output shape. It does not name or distinguish itself from any sibling tool, so it stops short of 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?

Usage is implied by '輸入一餐或一天吃的東西(中文)' — the agent can infer this applies when a user describes food they ate. But there is no explicit when-not guidance, no mention of adjacent tools (e.g. get_food_ad_violations or check_product_safety), and no note on what to do with non-Chinese input or ambiguous meal descriptions.

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