Skip to main content
Glama

查詢食藥署整理的國際食品安全警訊

get_international_food_alerts
Read-onlyIdempotent

查詢食藥署整理的國際食品安全警訊(各國回收、下架)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_international_food_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo最近幾天,預設 120
keywordNo產品、品牌或國家

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and side-effect profile are covered structurally. The description adds useful provenance (TFDA-compiled) and content scope (foreign-country recalls and removals), but says nothing about result volume, time-window behavior, or how openWorld data staleness should be treated.

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 with the resource named first and the scope qualifier in parentheses; there is no filler, hedging, or redundant restatement of the title.

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?

For a simple two-optional-parameter read-only list tool with no output schema, the description covers source and subject matter but never says what an alert record contains or what happens when no keyword is supplied. Annotations and a fully documented schema carry most of the remaining burden, leaving this adequate but not complete.

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?

Schema description coverage is 100% and both optional parameters (days with default 120, keyword covering product/brand/country) are fully documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 (查詢) and resource (食藥署整理的國際食品安全警訊), plus a parenthetical scope qualifier (各國回收、下架) that clarifies the content type. This distinguishes it implicitly from domestic siblings like get_food_ad_violations, but no sibling is named and the differentiation is only inferable from the word 國際.

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 only implied by the scope words 國際 and 回收、下架 — an agent can infer this is for international recall/withdrawal news rather than domestic violations. There is no explicit when-to-use statement, no mention of when to prefer get_food_ad_violations or get_drug_recalls, and no guidance on how to combine the days and keyword filters.

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.