Skip to main content
Glama

Get a guide

get_resource
Read-onlyIdempotent

Full text of one resource (kind + slug from list_resources). Text is capped at 20,000 characters.

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": {
      "kind": "<kind>",
      "slug": "<slug>"
    },
    "name": "get_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
slugYes
localeNoContent language: en, fa, ar or ckb.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds genuinely new behavior: the response text is capped at 20,000 characters, which warns the agent that long documents arrive truncated. It doesn't say whether truncation is signalled in the payload, which is the one remaining gap.

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 short sentences, zero filler, and the highest-value facts (what it returns, where the identifiers come from, the size cap) are all front-loaded.

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?

For a simple 3-parameter read tool with no output schema and annotations that cover safety, the description covers purpose, identifier provenance, and the truncation cap. It stops short of describing error behavior for invalid kind/slug pairs or whether locale falls back, but nothing essential to making the call is missing.

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 only 33% — only locale is documented in-schema; kind and slug are bare apart from enums and length bounds. The description partially compensates by explaining that kind+slug come from list_resources, but it says nothing about slug format (the 1–200 char constraint) or what happens with an unknown slug. Partial compensation justifies a 3 rather than a 2.

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?

States a specific verb+resource: 'Full text of one resource', with the identifying pair (kind + slug) named inline. It implicitly separates itself from list_resources by citing it as the source of the identifiers. Minor friction: the title says 'Get a guide' while the schema's kind enum covers guide/standard/datasheet/glossary, so the title is narrower than the tool.

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 parenthetical '(kind + slug from list_resources)' encodes the prerequisite workflow — the agent knows it must call list_resources first to obtain valid identifiers. There are no explicit exclusions or named alternatives for fetching content another way, but the context is clear enough to act on.

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