Skip to main content
Glama

Get related articles

get_related_articles
Read-only
Articles related to one article: other publishers' coverage of the same story and closely connected stories, best match first. Pass the id of an article from search_news or get_latest_news.

Matches on the article's words, so results are in the article's own language, published within 7 days either side of it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "article_id": "<article_id>"
    },
    "name": "get_related_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many related articles, 1 to 25. Default 10.
article_idYesThe id of an article from search_news or get_latest_news.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description adds genuinely useful behavioral facts the agent could not infer: matching is term-based on the article's own words, results come back in the article's language, and the corpus is limited to a +/-7 day window around the source article. Ordering (best match first) is also disclosed. These constraints materially shape how the agent should interpret and trust the results.

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?

Two compact sentences with the scope and result semantics front-loaded and the input requirement trailing. Every clause carries information - result composition, ordering, language, time window, id provenance - with no filler or repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only lookup with full schema coverage and a readOnlyHint annotation, the description supplies everything an agent needs: what the results are, how they are ordered, what language they will be in, how far back/forward they can come from, and where the required id must originate. No output schema exists, but the description adequately characterizes the return set.

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%, with both article_id and limit fully documented (including the 1-25 range and default 10), so the baseline is 3. The description only restates article_id's provenance from search_news/get_latest_news and adds nothing about limit; the 7-day window is a result constraint, not a parameter, so it earns no extra credit here.

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 the specific resource (articles related to one article) and characterizes the result set: other publishers' coverage of the same story plus closely connected stories, ordered best-match-first. That is far more than a restatement of the name. It stops short of a full 5 because 'other publishers' coverage' overlaps conceptually with the get_coverage sibling, and the description never draws that line.

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

Usage Guidelines4/5

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

It clearly establishes the entry condition: you must already have an article id, obtained from search_news or get_latest_news, so the agent knows this is a follow-up/expansion call rather than a discovery call. It gives no explicit exclusions (e.g., when to prefer get_coverage for publisher breakdowns), which keeps it out of 5 territory.

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