Skip to main content
Glama

Local news

news
Read-onlyIdempotent

Recent items from the network's town news desks; each summarizes a named public source with its link and date.

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

Input Schema

NameRequiredDescriptionDefault
townNoTown or county, e.g. "Hornell", "Watkins Glen", "Steuben County"
limitNo
topicNoe.g. openings, council, notices

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description usefully adds the return shape (each item carries a named source, link, and date), which matters because no output schema exists. It says nothing about how far back 'recent' reaches or how limit interacts with the feed.

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 well-formed sentence that front-loads the resource and then the record shape. No filler, nothing repeated from the schema or annotations.

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 no-output-schema tool, describing the returned item as source+link+date is genuinely helpful. But with zero required parameters, the description should clarify default behavior when town or topic is absent, and it leaves 'recent' undefined — gaps an agent would hit on first call.

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 coverage is only 67%, and the description adds no meaning to any of the three parameters — town, topic, and especially limit, which has bounds and a default but no textual description in the schema. With all params optional, the description also fails to say what happens when town is omitted, which is the key semantic question.

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 ('Recent items from the network's town news desks') and its content unit, and the notion of 'town news' distinguishes it from siblings like events, conditions, or indicators. It stops short of an explicit retrieve/list verb, but the resource is unambiguous.

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 statement of when to use this versus alternatives such as events or conditions, and no exclusions. The only usage signal is the word 'Recent', which implies a recency filter but is never defined or contrasted with anything.

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