Skip to main content
Glama

Get related published resources

get_related_resources
Read-only

Use this tool after you have a resource id and need a related published item that the catalog already records: the next or previous lesson, the course page, the song and its watch page, or a shared category or coloring gallery. It does not guess semantic similarity.

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

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
localeNoInterface locale code from the 77-locale registry, such as en, ru, ar, or zh-Hans.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond them: only catalog-recorded, published relations are returned, and relations are not inferred by similarity. It does not mention what happens when no relations exist or how results are ordered.

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 sentences, no filler. The usage trigger is front-loaded and the enumerated relation types plus the semantic-similarity exclusion each carry distinct information.

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 no output schema, the description usefully characterizes what comes back (curated relation types rather than ranked guesses). For a simple 3-parameter read tool this is close to sufficient, though result ordering, empty-result behavior, and the meaning of 'limit' remain unstated.

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 only 33% (only locale is documented in the schema), so the description needs to compensate. It clarifies that 'id' is a resource id for an already-known published item, but says nothing about 'limit' (1-20, presumably max results) or which locale applies to what. Partial compensation only.

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?

States a specific verb and resource (get related published resources for a given resource id) and enumerates the concrete relation types it can return: next/previous lesson, course page, song/watch page, shared category or coloring gallery. It also distinguishes itself from semantic-search siblings with the explicit line 'It does not guess semantic similarity.'

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?

Gives a clear precondition ('after you have a resource id') and a clear condition of need ('need a related published item that the catalog already records'), plus a negative condition ruling out semantic-similarity lookups. It stops short of naming which sibling to use instead when no id is available (e.g., search_resources).

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