Skip to main content
Glama

Get one published resource

get_resource
Read-only

Use this tool when you already have a stable ndf: resource id and need its published title, concise description, canonical URL, and language fields. Locale selects the interface version and defaults inside the catalog to en when omitted. It returns an error when that id or language version is not published.

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

Input Schema

NameRequiredDescriptionDefault
idYes
localeNoInterface locale code from the 77-locale registry, such as en, ru, ar, or zh-Hans.
learningLanguageNoInterface 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

A3.6/5.0
Behavior3/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 safety is covered. The description adds genuine value beyond them by disclosing the locale default (en when omitted) and the error behavior for unpublished ids/locales. It does not say anything about response shape beyond the field list, caching, or what an unpublished 'language version' means operationally.

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: precondition and payload first, then the locale default, then the error case. No filler or repetition. Minor cost is that the second and third sentences are somewhat compressed, mixing default behavior with failure behavior.

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 carries the return-value burden and does so by enumerating the returned fields, plus it discloses the default and the error condition. The remaining gap is the unexplained second locale-like parameter, which an agent would need to understand to call the tool confidently.

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 67%, and the description meaningfully supplements the 'locale' parameter by stating it selects the interface version and defaults to en. However, 'learningLanguage' is never mentioned, and its schema text is identical to locale's, so the description does nothing to resolve how the two differ or how they interact.

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 a specific verb (retrieve) and resource (a published ndf: resource by stable id) and enumerates the returned fields (title, concise description, canonical URL, language). The precondition 'when you already have a stable ndf: resource id' implicitly separates it from search_resources, but no sibling is named explicitly, so it falls just short of full differentiation.

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 gives a clear when-to-use condition: you must already hold a stable ndf: resource id, which rules out discovery-style usage. It also states the failure condition (error when the id or language version is not published), but never names an alternative tool to use when you do not have an id, and gives no guidance on choosing among locale vs learningLanguage.

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