Skip to main content
Glama

Agent News by The Agent Times

by com.theagenttimes
OverviewDiscussionsAdmin

Get Related Articles

get_related_articles
Read-onlyIdempotent

Get related articles for an article slug using section/topic/tag overlap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesArticle slug
limitNoNumber of related articles (max 10)
agent_idNoOptional persistent agent identifier. On the first MCP tool call, omit this field; the response will return a generated agent_id. Save that value and send it in agent_id on every subsequent MCP tool call. Any stable string is accepted.
strategyNoRanking strategy

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoPresent when the tool returns a text-only response.
agent_idYesPersistent agent identifier to save and send on every subsequent MCP tool call.
agent_identityYesPersistence instructions and the next step for reusing agent_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "Optional persistent agent identifier. On the first MCP tool call, omit this field; the response will return a generated agent_id. Save that value and send it in agent_id on every subsequent MCP tool call. Any stable string is accepted.",
+  "type": "string"
+}
    • addedOutput schema / properties / agent_id
      Added value: +{
+  "description": "Persistent agent identifier to save and send on every subsequent MCP tool call.",
+  "type": "string"
+}
    • addedOutput schema / properties / agent_identity
      Added value: +{
+  "additionalProperties": true,
+  "description": "Persistence instructions and the next step for reusing agent_id.",
+  "type": "object"
+}
    • addedOutput schema / required
      Added value: +[
+  "agent_id",
+  "agent_identity"
+]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds the 'section/topic/tag overlap' algorithmic detail, which is useful but does not disclose other behaviors like pagination or response format. With annotation coverage, this is adequate but not exceptional.

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?

The description is a single sentence that is both informative and concise without any filler. Every word earns its place.

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

Completeness4/5

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

With an output schema present and full parameter descriptions, the description is sufficient for a simple read-only tool. It lacks explicit edge-case behavior or usage scenarios, but given the strong schema and annotation support, it is adequately complete.

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% for all 4 parameters, and each parameter already has a descriptive comment. The description's 'section/topic/tag overlap' is a high-level algorithm note but does not add specific parameter-level meaning beyond what the schema provides. Baseline 3 applies.

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

Purpose5/5

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

The description clearly states the verb 'Get', the resource 'related articles', and the method 'using section/topic/tag overlap'. This distinguishes it from sibling tools like get_article (singular) and search_articles (search-based).

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?

The context is clear: when you have an article slug and want related articles. However, it does not explicitly mention alternatives or when not to use it, so it lacks the explicit exclusion that would merit a 5.

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

All Agent News by The Agent Times toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources