Skip to main content
Glama

List groups

list_groups
Read-onlyIdempotent

Browse group authorities by name, mostly performing ensembles credited on research items, with item counts and citation links.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50, max 200
offsetNo
keywordNoName or acronym, partial; several words must all match

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Name or acronym, partial"New value: +"Name or acronym, partial; several words must all match"
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  4. Changed2 schema fields changed
    • addedInput schema / properties / keyword / description
      Added value: +"Name or acronym, partial"
    • addedInput schema / properties / keyword / maxLength
      Added value: +1000
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds genuinely new behavioral context — that entries are authorities, mostly performing ensembles, and that results carry item counts and citation links. It does not mention paging behavior or ordering, keeping it from 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.

Conciseness5/5

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

A single sentence with zero filler, front-loaded on the verb and resource, then the entity meaning and return contents. Nothing is repeated and nothing is wasted.

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, zero-required-parameter list tool with no output schema, the description covers what is listed, how to filter, and what fields come back, while annotations carry the safety profile. Only the lack of result-ordering/total-count context and sibling routing keeps it below 5.

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 67% and the schema itself documents limit (default 50, max 200) and keyword (name or acronym, partial, multi-word AND matching). The description's "by name" is narrower than the actual acronym support in the schema and adds no meaning for the undocumented offset parameter, so it does no more than the schema already does.

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?

"Browse group authorities by name" gives a clear verb+resource, and the description further specifies that these are mostly performing ensembles credited on research items, plus what comes back (item counts, citation links). It never names or contrasts a sibling (e.g., get_entity_graph, resolve_entity), so it falls just short of 5.

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?

"Browse ... by name" implies a discovery/paging use case with keyword filtering, which is a usable hint. However, there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for looking up an individual group, so the agent must infer.

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.