Skip to main content
Glama

玩具品牌官方網站新聞

toys__official_toy_news
Read-onlyIdempotent

[NEW玩具情報站]玩具品牌官方網站新聞:新品、發售日、延期、活動(Good Smile、萬代模型、TAKARA TOMY、MegaHouse、壽屋、LEGO)。

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

Input Schema

NameRequiredDescriptionDefault
zoneNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already state readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds domain context (which brands, which news categories) but says nothing about freshness, aggregation behavior, or what happens when no news matches — modest added value beyond annotations.

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 compact sentence with the topic front-loaded and the brand list as scannable parenthetical detail; the bracketed station label adds little but costs almost nothing. No filler or repetition.

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 two undocumented parameters, no output schema, and no explanation of the region filter or result count, an agent calling this tool must guess how zone and limit change results. For a read-only news feed this is not catastrophic, but the definition leaves the call-shaping information entirely to the schema.

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% for both parameters, and the description mentions neither 'zone' nor 'limit'. The 亞洲/美國/歐洲 enum values are visible in the schema, but whether zone filters by brand origin, event location, or readership region is never clarified, and the meaning/limits of 'limit' are unexplained. The description therefore does not compensate for the total coverage gap.

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 resource (official brand-website toy news) and enumerates the content types it covers — new products, release dates, delays, events — plus the brands involved (Good Smile, Bandai, TAKARA TOMY, MegaHouse, Kotobukiya, LEGO). That is far more specific than a restatement of the name. It stops short of distinguishing itself from siblings such as toys__latest_toy_news or toys__official_toy_videos, so it is clear but not fully disambiguating.

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?

The 'official website news' framing and the brand list implicitly tell an agent this is for manufacturer-sourced announcements rather than general toy news or videos. However, there is no explicit when-to-use statement, no exclusion, and no named alternative, so the routing decision is left to inference.

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