Skip to main content
Glama

cOBD

List news

list_news
Read-onlyIdempotent

The latest public posts, newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return, 1 to 25. Default 10.

Output Schema

NameRequiredDescriptionDefault
postsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds two genuinely useful behavioral facts beyond that: results are ordered newest first, and only public posts are returned. It says nothing about pagination or how much content is available, but with annotations carrying the safety burden a 3 is fair.

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 short clause with zero padding, and the ordering constraint is front-loaded. Its brevity edges toward under-specification rather than verbosity, but nothing is wasted.

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?

This is a simple one-optional-parameter read tool with an output schema, so return values need not be explained and annotations cover safety. The remaining meaningful gap is sibling routing against read_news, which the description leaves unaddressed.

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 coverage is 100% and the single 'limit' parameter already documents its 1-25 range and default of 10 in the schema. The description adds no meaning about the limit or about how ordering interacts with truncation, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'The latest public posts, newest first' conveys a listing of recent public content, with 'list' supplied only by the tool name. It never uses the word 'news' and gives no basis for choosing it over the sibling read_news, leaving the object of the listing (posts vs. news items) somewhat ambiguous.

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?

'Latest' implies a browsing/feed use case, but there is no explicit when-to-use statement, no mention of read_news as the alternative for fetching a specific item, and no stated preconditions. An agent must infer routing entirely from the tool name.

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