Skip to main content
Glama

Get assembly

get_assembly
Read-onlyIdempotent

Return one assembly's formula, required dimensions, material factors, purchase increment, sources, and material-pack lineage.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "assembly_type": "<assembly_type>"
    },
    "name": "get_assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault
assembly_typeYesAssembly id, for example concrete_slab; see list_assemblies.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / assembly_type / description
      Added value: +"Assembly id, for example concrete_slab; see list_assemblies."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered without the description. The description adds a preview of payload contents, which is modest extra context since an output schema exists. Nothing is said about behavior on an unknown assembly id (error vs empty result), which is the main remaining behavioral gap.

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 every clause earning its place by naming a returned field. No boilerplate, though the field enumeration is fairly long and largely mirrors the output schema.

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 single-parameter read tool with full schema coverage, complete annotations, and an output schema, the description is sufficient for correct invocation. It only lacks error/not-found behavior, which the output schema may partially cover.

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 100% and the single parameter assembly_type is already documented in the schema with an example value and a pointer to list_assemblies. The description adds no format, casing, or validity semantics beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Return) and resource (one assembly) and enumerates exactly what comes back: formula, required dimensions, material factors, purchase increment, sources, material-pack lineage. The singular 'one assembly' distinguishes it from the sibling list_assemblies, and the schema description completes the routing hint.

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 lookup you call once you have an assembly id, and the parameter description points at list_assemblies for discovery. There is no explicit when-to-use or when-not-to-use statement, and no mention of alternatives such as calculate_takeoff or get_material_pack.

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.