Skip to main content
Glama

List guides and resources

list_resources
Read-onlyIdempotent

Published technical guides, standards notes, datasheets and glossary entries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNoMax rows (1-20).
queryNo
localeNoContent language: en, fa, ar or ckb.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds only the published-content scope and says nothing about ordering, default result size, whether query searches titles/content, or locale effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact phrase with no waste and front-loads the content types. However, it is a noun fragment rather than a statement of the operation, so the structure is only adequate.

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

Completeness2/5

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

For a four-parameter list endpoint with no output schema, the definition lacks the action, pagination/result-size behavior, query semantics, and usage boundaries. Rich read-only annotations cover safety, but not enough to make the definition 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 50%: limit and locale are documented in the schema, while kind and query are not. The description enumerates the resource types that map to the kind enum, but it does not explain query or how kind, limit and locale interact, so it only partially compensates.

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

Purpose3/5

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

The description names the content domain — technical guides, standards notes, datasheets and glossary entries — which distinguishes it from product/service siblings. However, it never states the action 'list' or what is returned, leaving the agent to infer listing from the tool name and title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no routing to alternatives such as get_resource for a single item or search for text search. The agent must infer from the name that this is the collection endpoint.

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