Skip to main content
Glama

List assemblies

list_assemblies
Read-onlyIdempotent

List supported assemblies, required dimensions, formulas, waste defaults, and the current material-pack digest.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered structurally. The description adds scope value by disclosing what each assembly record exposes and that the material-pack digest reflects the 'current' state, but says nothing about result size, ordering, or whether the catalog changes over time.

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?

One front-loaded sentence with no filler; the trailing field list is dense but every element maps to real output content. Slightly compressed phrasing ('material-pack digest') is the only friction.

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?

With no parameters and an output schema present, the definition does not need to explain return structure, and it is nearly complete. The remaining gap is relational: it never tells the agent how the returned assemblies connect to get_assembly or calculate_takeoff, which matters in a six-sibling toolset.

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

Parameters4/5

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

Zero parameters, so the schema constraint baseline of 4 applies. The description correctly implies a no-argument call by describing a global catalog rather than a filtered query.

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?

Uses a specific verb (List) on a specific resource (assemblies) and enumerates the fields each entry carries: dimensions, formulas, waste defaults, material-pack digest. An agent can separate it from get_assembly (singular retrieval) by the plural listing framing, though no sibling is named outright.

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: 'List supported assemblies' suggests a catalog/browse operation that precedes get_assembly for details, but the description never states when to call this instead of get_assembly or list_material_pack, nor any prerequisites.

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.