Skip to main content
Glama

cad_apps

Read-onlyIdempotent

Lists every supported CAD, BIM, and 3D app with its current reachability so you can confirm availability before running scripts; set only_available to hide unreachable apps.

Instructions

List every app OmniBridge supports and whether it is reachable right now.

Call this first. An app is usable when its state is "connected" or "running". When the state is "running, bridge not loaded", tell the user the next step. Set only_available to true to hide apps that are not running.

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

Input Schema

NameRequiredDescriptionDefault
only_availableNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: it defines what 'usable' means in terms of state values and prescribes a follow-up action ('tell the user the `next` step') when the state is 'running, bridge not loaded'. It does not discuss rate limits or pagination, but for a read-only listing call that is a minor omission.

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?

The purpose is front-loaded in the first sentence, followed by short directive sentences with no filler. Every line carries actionable information: ordering, state semantics, follow-up behavior, and the filter flag.

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?

An output schema exists, so return values need not be described, and the description appropriately focuses on interpretation and next steps instead. With one parameter, no nesting, and annotations covering safety, the definition is nearly complete; the only residual gap is the imprecise interaction between the 'usable' state definition and the only_available filter.

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?

Schema description coverage is 0% and the single parameter has no schema description, so the description must carry the load — and it does: 'Set only_available to true to hide apps that are not running' explains the flag's effect and default behavior. There is a slight ambiguity, since usability is defined as 'connected' or 'running' while the filter is phrased only in terms of 'not running', leaving it unclear whether a connected-but-not-running app is hidden.

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 opens with a specific verb and resource: 'List every app OmniBridge supports and whether it is reachable right now.' That is far more informative than the bare name 'cad_apps' and defines scope precisely (all supported apps + reachability). It never explicitly contrasts itself with the sibling tools (cad_modify, cad_read, cad_screenshot, cad_skill), so it lands at 4 rather than 5.

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?

'Call this first' gives explicit ordering guidance that an agent can act on, and the definition of a usable app ('connected' or 'running') tells the agent how to interpret results before choosing a follow-up call. It stops short of naming alternatives or stating when *not* to call it, so it is strong context without full when/when-not coverage.

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

Deploy Server

Other Tools