get_newsLatest Uruguayan dollar/economy headlines (Google News), de-duplicated and newest first.
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_news"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max headlines (default 12) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond that: results are de-duplicated, ordered newest first, and sourced from Google News. It does not describe freshness windows or pagination behavior, but the annotations carry much of the safety profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single front-loaded sentence with no wasted words. Source, scope, de-duplication, and ordering are all stated efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read-only headline tool with rich annotations and no output schema, the description supplies the key context an agent needs: source, domain, ordering, and de-duplication. Nothing essential is missing for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter is fully documented in the schema with its maximum, default, and meaning. The description does not add parameter-specific detail, so the baseline of 3 is appropriate when schema coverage is 100%.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific resource and scope: latest Uruguayan dollar/economy headlines from Google News. It is clearly distinguishable from all sibling finance, rental, and car tools, which do not provide news headlines.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The content implies this is the tool for recent Uruguayan economy/dollar news, but it does not explicitly say when to use it versus alternatives or when not to use it. With no direct news sibling, the guidance is adequate but only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.