Skip to main content
Glama

Powiązane artykuły

related_articles
Read-only

Find articles related to a given one by semantic similarity and shared topics, people, or places, helping you discover connected content in the archive.

Instructions

Finds articles related to the given one – by meaning (semantic similarity of the whole text) and by shared topics, people and places from the AI notes.

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": {
      "id": "<id>"
    },
    "name": "related_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid albo tytuł artykułu
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden; it usefully discloses the relevance mechanism (semantic similarity plus entity overlap from AI notes), which is real behavior beyond the annotations. It says nothing about result ordering, whether scores are returned, or how the two signals are combined, so an agent cannot predict the response shape.

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 front-loaded sentence with the core purpose first and the qualifying mechanism after the dash. There is no filler, no restatement of the title, and every clause carries information.

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 two-parameter read-only tool with no output schema, the description covers what it does and why results are considered related, which is close to sufficient. It still leaves result ordering, approximate return volume beyond the schema default, and the absence of any traversal/follow-up guidance 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 50%: 'id' is documented in the schema as accepting an id or an article title, while 'limit' has only a default of 8 and a 1-20 range with no prose meaning. The description adds no parameter detail at all and does not clarify that limit controls how many related articles are returned, so it neither compensates for the gap nor detracts.

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 states a specific verb ('finds') and resource ('articles related to the given one') and explains the two relevance signals: whole-text semantic similarity and shared topics, people and places from AI notes. That distinguishes it from a plain keyword search or a single-article reader, though it never names the closest sibling (search_by_meaning), so differentiation is left to inference.

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 implied by 'related to the given one', which frames this as a follow-on/discovery step after an article is known. There is no explicit when-to-use versus when-not-to-use, no mention of how it differs from search_by_meaning or search, and no stated prerequisites for the referenced article.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.