Skip to main content
Glama

catalog_list

Read-only

Lists supported logical devices and pins, letting you set library_path to resolve ambiguous installed devices. Use it to browse the catalog, not to verify placement.

Instructions

List supported logical devices and pins; library_path explicitly selects ambiguous installed devices. NOT placement verification.

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": "catalog_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
library_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered and the description only needs to add context. It adds the meaningful qualifier "supported" (only catalog-recognized devices are returned) but says nothing about result size, ordering, or how the two parameters combine.

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 clauses plus a short negation, front-loaded with the capability before the parameter note and the exclusion. The trailing fragment "NOT placement verification" is terse but earns its place as an explicit anti-use case; nothing is padded.

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?

There is no output schema, so the description should hint at the return shape, yet it only says the tool lists devices and pins without describing the item structure or whether pins nest under devices. For a two-parameter read-only catalog lookup this is workable but leaves a substantive gap.

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 carries the full burden; it explains library_path well, conveying that it disambiguates between multiple installed devices of ambiguous identity. The `device` parameter is never mentioned, so an agent cannot tell whether it is a filter, an exact name, or a logical-device selector.

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+resource ("List supported logical devices and pins") and immediately scopes the result set to supported logical entities, which separates it from the mutation and export siblings. It does not explicitly contrast with library_device or library_search, so the boundary against those lookup tools stays implicit.

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?

It names a usage condition for one parameter (use library_path when installed devices are ambiguous) and rules out a misuse ("NOT placement verification"), which is more than most definitions offer. However, it never names the tool that does perform placement verification, leaving the agent to guess the correct alternative from the sibling list.

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