Skip to main content
Glama

List concepts

list_concepts
Read-only

List concepts by name, optionally only the members of one tag.

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 list members of this tag. Leave out to list all.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/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 externally. The description adds little beyond that—only that results are ordered 'by name' and that tag filtering narrows to members—and says nothing about volume, pagination, or whether a tag with no members returns empty versus an error.

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?

A single front-loaded sentence with no filler; the optional filter is presented after the core action. Nothing is redundant enough to remove.

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?

This is a zero-required-parameter read tool with one fully documented parameter and complete annotations, so the description needs to do very little. The residual gaps—the meaning of 'by name' (sorted? looked up?) and the shape of the returned list—are modest but real, especially since there is no output schema.

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% and the sole parameter already carries 'Only list members of this tag. Leave out to list all.' The description restates that same semantics rather than adding anything new, so the baseline of 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 and resource ('List concepts') plus a scoping/ordering hint ('by name') and the tag filter. It never names or distinguishes itself from siblings such as search_keyword, search_semantic, or read_concept, so an agent must infer the boundary between 'list' and 'search' on its own.

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 only implied: 'optionally only the members of one tag' tells the agent that omitting the parameter enumerates everything, which is a when-to-use-per-parameter hint rather than a when-to-use-this-tool guidance. There is no statement about when to prefer the search siblings or read_concept instead.

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