Skip to main content
Glama

Physical Capability Cloud

get_build_options

Get configuration options for a capability type: parameter groups, each parameter's definition, and a base price hint. It includes no assurance tiers. Use before calling calculate_price.

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": {
      "type": "<type>"
    },
    "name": "get_build_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesCapability type (e.g. fdm, cnc-3axis, hplc)
profileIdNoOptional capability profile ID
selectionsNoCurrent selections to refine available options

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior1/5

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

The description calls this a 'Get' operation, which strongly implies a read-only lookup, while the annotations declare readOnlyHint=false. That inconsistency means the agent cannot trust whether invoking this tool has side effects, and the description does not disclose any mutation, caching, or other write-like behavior.

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?

Two compact sentences with the core purpose, return contents, exclusion, and workflow guidance front-loaded. There is no filler or repetition.

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?

With no output schema, the description helpfully lists the returned data (parameter groups, parameter definitions, base price hint) and notes the absence of assurance tiers. It is reasonably complete for a configuration lookup, though the readOnlyHint discrepancy leaves the tool's side-effect profile unresolved.

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%, so the three parameters are already fully documented in the input schema. The description adds only that the tool operates on a 'capability type', which aligns with the existing 'type' parameter but does not add syntax or meaning beyond the schema.

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?

The description states a specific verb and resource ('Get configuration options for a capability type') and enumerates what is returned: parameter groups, each parameter's definition, and a base price hint. It also distinguishes itself from related pricing work by noting that it includes no assurance tiers and should be used before calculate_price.

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 explicit sequencing guidance ('Use before calling calculate_price'), which tells the agent when this tool fits into a workflow. It does not state when not to use it or name alternatives besides calculate_price, but the usage context is clear.

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.