Skip to main content
Glama

library_concepts

Areas and concept titles of a collection (free). Free.

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>"
    },
    "name": "library_concepts"
  }
}

Input Schema

NameRequiredDescriptionDefault
colYesCollection id
langNoLanguage of the core texts (default it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and largely fails it. The only behavioral signal is '(free). Free.', which usefully implies no credit/quota cost, but nothing is said about what is returned, ordering, pagination, or whether a nonexistent collection errors or returns empty.

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

Conciseness2/5

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

The single sentence is short and front-loaded, but '(free). Free.' duplicates the same information redundantly, and the duplicated slot could have carried the missing verb or the return-shape detail. Waste at this length is proportionally significant.

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?

The tool is simple (one required enum parameter) and the input schema is rich, but there is no output schema, so the description should describe what a result looks like ('areas and concept titles' only gestures at it). With no annotations and no return-value detail, an agent cannot tell what it will receive or how it differs from 'library_concept'.

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 100% with enums for both 'col' and 'lang', so the schema already documents valid values and the 'lang' default of 'it'. The description adds no meaning beyond this, which is the expected baseline when the schema does the heavy lifting.

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 resource ('areas and concept titles of a collection') but supplies no verb, so it is unclear whether this lists, fetches, or summarizes. It also does not differentiate itself from the near-identical sibling 'library_concept' or from 'library_glossary'. The intent is loosely inferable but not stated with a specific operation.

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, no exclusions, and no routing to the singular 'library_concept' or 'library_collections' alternative. The agent must infer the selection criteria from the tool name and parameter shape 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