Skip to main content
Glama

Diffusion Love Knowledge

Read news for followed topics

news_updates
Read-onlyIdempotent

Feed items matching any of the given tags, project families or organizations, newest first, from the live news snapshot. At most 20 values in total and 50 items. Values the feed does not know are listed under "unknown".

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

Input Schema

NameRequiredDescriptionDefault
orgsNo
tagsNo
limitNo
sinceNo
familiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are newest-first, the response is capped at 50 items, and unrecognized values are echoed under an "unknown" key. That last detail is especially valuable with no output schema. It does not describe the fields on each item.

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?

Three tight sentences with the resource and scope front-loaded, then caps, then the unknown-value behavior. No filler or restatement of the tool name. The cap sentence is slightly compressed ('At most 20 values in total and 50 items') but still parseable.

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 five-parameter, zero-coverage read tool with no output schema, the definition covers selection semantics and result caps but leaves two real gaps: the expected format of `since`, and what an item record contains. Adequate to call correctly in the common case, incomplete for an agent that needs to construct a time window.

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 must carry the load, and it only partly does. It maps to three of five parameters (tags, families, orgs) and usefully clarifies that the 20-value cap is a combined total across them rather than per-array as maxItems=20 in the schema suggests. However, `since` (maxLength 10) has no format or semantics explained at all, and `limit` is left to the schema bounds.

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?

States a specific verb and resource: feed items matching tags, project families or organizations, from the live news snapshot, newest first. An agent can tell this is a filtered news reader rather than a search or project-update tool. It stops short of naming project_updates or search_knowledge as the alternatives it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by 'from the live news snapshot' and the filter vocabulary; there is no explicit 'use this when following topics, use project_updates when...' routing guidance. The 'newest first' and cap statements describe output shape, not when to select this tool over a sibling.

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