Skip to main content
Glama

library_concept

Full concept entry: summary, deep dive in parts, subtopics, included concepts and explained links to related concepts. Price: $0.005 USDC per call (x402).

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": {
      "col": "<col>",
      "id": "<id>"
    },
    "name": "library_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesConcept id from /v2/{col}/concepts
colYesCollection id
langNoLanguage of the core texts (default it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the per-call price and x402 payment protocol, and it describes the shape of the returned entry. However, it does not explain payment mechanics, authentication, rate limits, error behavior, or whether a failed/partial response still incurs cost.

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?

The definition is two tight sentences with no filler. The primary content description is front-loaded and the pricing caveat follows immediately, so every sentence earns its place.

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 retrieval tool with a fully described three-parameter schema, the description is largely complete: it explains the returned content and notes the per-call cost. The main omission is when to choose this tool over sibling concept or search tools, but no critical calling information 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 100%, so the schema already documents col, id, and lang, including enum values and defaults. The description adds no parameter-specific meaning beyond what the schema provides, making the baseline 3 appropriate.

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 clearly identifies the resource as a full concept entry and enumerates what it contains: summary, deep dive, subtopics, included concepts, and explained links. It does not explicitly distinguish itself from sibling tools such as library_concepts or library_search, but the purpose is understandable without opening the schema.

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 explicit guidance on when to use this tool versus alternatives such as library_concepts, library_search, or library_glossary. Usage is only implied by the phrase 'Full concept entry,' and the description provides no exclusions, prerequisites, or routing advice.

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