Skip to main content
Glama

news_latest

Fetch recent Westlake University news entries, with an optional limit to control how many campus news items are returned.

Instructions

西湖新闻最新条目。

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

Input Schema

NameRequiredDescriptionDefault
limitNo最多返回条数,默认 10。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and delivers almost nothing: it does not confirm this is a read-only operation, does not state ordering (recency?), the source of the news, or what happens when no items exist. Only the bare concept of 'latest items' is conveyed.

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?

It is a single short sentence with zero filler and the key qualifier ('最新') front-loaded. The brevity is efficient, though it edges into under-specification rather than tight conciseness.

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-parameter read tool with no output schema, the essentials are barely covered: the agent knows what it fetches but not what fields the items carry, what '西湖' refers to exactly, or how recency is defined. Marginally adequate, with real gaps.

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 the single 'limit' parameter is fully documented in the schema (1-50, default 10), so baseline 3 applies. The description adds no meaning beyond the schema, such as how results are ordered when the limit truncates the list.

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 concrete resource plus a scope qualifier ('西湖新闻' + '最新条目'), so an agent can tell it returns recent news items rather than search results or archives. It stops short of distinguishing itself from other '*_latest' siblings (research_latest, career_latest), so it is clear but not differentiated.

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?

There is no guidance on when to call this versus researching news through wiki_search/site_search or the other '_latest' tools, and no stated exclusions or prerequisites. The word '最新' implies fresh-content use, but that is inference rather than instruction.

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