Skip to main content
Glama

list_concept_families

Read-onlyIdempotent

Lists curated concept families and variable counts so agents can browse the semantic vocabulary in paginated, family-code order.

Instructions

List the concept families (the curated semantic vocabulary) + variable counts.

Paginated with the same limit (1..1000) / offset semantics as list_concepts, ordered by family code.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: results are paginated, ordered by family code, and include variable counts. It does not mention total counts or what happens at the end of the result set, which keeps it short of a 5.

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

Conciseness4/5

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

Two short sentences, front-loaded with the purpose and followed by the pagination contract. No filler, though the cross-reference phrasing ('the same ... semantics as list_concepts') is slightly indirect compared to stating the behavior outright.

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?

An output schema exists, so return values need no explanation, and the description covers the two things an agent still needs: pagination bounds and result ordering. The only shortfall is that offset behavior is delegated to a sibling rather than described here.

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 0%, so the description must carry the load. It supplies the meaningful constraint the schema lacks (limit range 1..1000) and names offset, but defers the actual offset semantics to list_concepts by reference rather than stating them, leaving the second parameter only partially explained.

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?

States a specific verb and resource ('List the concept families') and clarifies what the resource is ('the curated semantic vocabulary') plus what is returned ('variable counts'). It is distinguishable from list_concepts, though the differentiation is only implicit via the pagination reference rather than an explicit contrast.

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: an agent can infer this is the discovery call for family codes before drilling into list_concepts. There is no explicit statement of when to prefer this over list_concepts or list_concept_mappings, and no prerequisites or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.