Skip to main content
Glama

Read concepts

read_concept
Read-only

Read one or more concepts (memory nodes) in full, by name or ID. Each ends with related concepts to consider opening next, with when to open them.

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": {
      "concepts": "<concepts>"
    },
    "name": "read_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
conceptsYesNames, other names or IDs of the concepts to read.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/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 genuinely new behavioral context: the response is structured with trailing related concepts and guidance on when to open them, which is the key thing an agent needs to plan multi-step exploration. It does not say what happens when a name/ID is missing or ambiguous.

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 with zero filler; scope and identifier forms come first, then the output characteristic that affects follow-up actions. Every sentence carries 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 compensates by describing the related-concepts trailer as part of the return value, and it covers identifier flexibility. Missing only edge-case behavior (unknown concept, truncation of large memory nodes), which keeps it short of a 5.

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%, so the single array parameter and its accepted identifier forms are already documented. The description's 'by name or ID' restates the schema rather than adding constraints, limits, or formatting rules, so baseline 3 applies.

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 gives a specific verb ('Read') plus resource ('concepts (memory nodes)') and scopes it ('one or more ... in full', 'by name or ID'). The 'in full' phrasing implicitly distinguishes it from listing/searching siblings, but no sibling is named, so differentiation is left to inference.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: you read full concepts when you need their complete content, and the returned related-concept list guides subsequent reads. There is no explicit when-not guidance (e.g. use list_concepts to browse, or search_* to find by content), so the agent must infer boundaries from sibling names alone.

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