Skip to main content
Glama

List concepts

list_concepts
Read-only

Enumerate concept metadata (no bodies), optionally filtered by product, type, or a single tag. Use to get the lay of the land in an unfamiliar vault, to audit what exists (e.g. all decisions for a product), or when search vocabulary isn't matching. For content, follow up with get_concept or get_context.

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_concepts"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly concepts carrying this tag.
typeNoOnly concepts of this type.
productNoOnly concepts of this product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "concept",
      -  "domain",
      -  "feature",
      -  "story",
      -  "spec",
      -  "workflow",
      -  "task",
      -  "decision",
      -  "constraint",
      -  "pattern",
      -  "glossary",
      -  "iteration",
      -  "milestone"
      -]New value: +[
      +  "concept",
      +  "domain",
      +  "feature",
      +  "story",
      +  "spec",
      +  "workflow",
      +  "task",
      +  "decision",
      +  "constraint",
      +  "pattern",
      +  "glossary",
      +  "iteration",
      +  "milestone",
      +  "epic"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "concept",
      -  "domain",
      -  "feature",
      -  "story",
      -  "spec",
      -  "workflow",
      -  "task",
      -  "decision",
      -  "constraint",
      -  "pattern",
      -  "glossary"
      -]New value: +[
      +  "concept",
      +  "domain",
      +  "feature",
      +  "story",
      +  "spec",
      +  "workflow",
      +  "task",
      +  "decision",
      +  "constraint",
      +  "pattern",
      +  "glossary",
      +  "iteration",
      +  "milestone"
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are metadata only with bodies excluded, and only a single tag can be filtered at a time. It stops short of saying whether results are paginated or capped, which matters for a listing call in a large vault.

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 sentences, front-loaded with the scope boundary (metadata, no bodies) before the use cases. Every clause carries information — the filter list, the three scenarios, and the follow-up routing — with no restatement of the title or annotations.

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 does the necessary work of telling the agent what comes back (concept metadata without bodies) and how to get the rest. It never states result volume, ordering, or pagination behavior, which is the remaining gap for a zero-required-parameter listing tool that could return everything in a vault.

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 all three filters are already documented and the baseline of 3 applies. The one addition beyond the schema is the "single tag" constraint, though listing filters with "or" leaves it slightly ambiguous whether product/type/tag compose or are mutually exclusive.

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

Purpose5/5

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

"Enumerate concept metadata (no bodies)" gives a specific verb, a specific resource, and the key scope boundary — metadata only, not content. The parenthetical explicitly separates it from get_concept/get_context, so an agent can tell the listing and retrieval tools apart without opening either schema.

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

Usage Guidelines5/5

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

Names three concrete situations to reach for it (unfamiliar vault, auditing existence such as all decisions for a product, search vocabulary not matching) and routes the agent onward to get_concept/get_context when actual content is needed. The "search vocabulary isn't matching" case implicitly positions it as the fallback to term search, which is the decision an agent actually faces.

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