Skip to main content
Glama

最新網友情報

toys__latest_toy_news
Read-onlyIdempotent

[NEW玩具情報站]最新網友情報:官方消息、新聞、謠傳、展示影片、開箱、討論。

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__latest_toy_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already state readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description does add one genuinely useful behavioral signal beyond that: results mix rumor (謠傳) and discussion content with official announcements, warning the agent that not everything returned is verified. It says nothing about result volume, ordering, recency window, or what an empty feed looks like.

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 source label and a compact enumeration; nothing is padded and the category list carries the parameter mapping. The bracketed site tag is borderline noise but small enough not to hurt scanability.

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 one-optional-enum read tool with no output schema, the definition covers what the tool returns categorically and warns that rumor content is included. It still leaves the default behavior, result format, and relationship to the more specific official-news siblings unexplained, which is the main gap given the crowded sibling set.

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 0%, so the description is the only place the six enum values get human meaning, and mapping 官方消息/新聞/謠傳/展示影片/開箱/討論 onto official/news/rumor/video/unbox/discuss is real added value. However, it never says the parameter is a filter, never states which category is returned when the optional type is omitted, and never says whether one type or a mix comes back.

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?

"最新網友情報" together with the category list (官方消息、新聞、謠傳、展示影片、開箱、討論) tells an agent this tool surfaces recent crowd-sourced toy news spanning multiple content kinds. The kind of resource is clear, but the definition never distinguishes itself from neighbors such as toys__official_toy_news or toys__official_toy_videos, so a reader cannot tell why to pick this aggregator over the specialized feeds.

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?

The description only labels the content; it gives no when-to-use rule, no when-not-to-use, and never points at the sibling tools that cover a subset of the same material. An agent must guess whether this is the broad catch-all or the official-only feed, which is exactly the distinction that matters here.

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