Skip to main content
Glama

list_modules

Read-only

Lists available modules and libraries one per line, with an optional filter, so you can check what exists before designing a block.

Instructions

The shelf, then each library (modules named library/Name), one line a module. Look here before designing a block.

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

Input Schema

NameRequiredDescriptionDefault
filterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral context about the return shape (library headers, one module per line, modules named library/Name), which matters since no output schema exists, but it leaves the filter behavior, result limits, and pagination unaddressed.

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 compact sentences with no filler, and the output-structure note is front-loaded before the usage hint. Brevity is appropriate, though the terse jargon phrasing ('The shelf') slightly harms readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, read-only listing tool with one optional parameter, the description gives a reasonable picture of what comes back and when to use it. However, the undefined 'filter' parameter and the unexplained 'shelf' concept leave gaps an agent would need to resolve by trial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'filter' parameter has 0% schema description coverage, so the description carries full responsibility for explaining it. It never mentions the parameter, what filtering applies to (module names? libraries?), or its syntax, leaving the agent to guess.

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 conveys that this enumerates modules grouped by library ('The shelf, then each library'), which is a specific resource listing, but the phrasing is cryptic and assumes domain knowledge of what 'the shelf' and 'library/Name' mean. It never plainly states 'list available modules/libraries' and doesn't distinguish itself from siblings like list_parts or list_circuits beyond the module/library scope.

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

Usage Guidelines4/5

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

It gives an explicit contextual directive: 'Look here before designing a block,' which tells the agent when this tool is relevant in a workflow. No alternatives or when-not conditions are named, but the usage context is clear rather than merely implied.

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