Skip to main content
Glama

cad_skill

Read-onlyIdempotent

Retrieve the app-specific scripting guide covering language, predefined names, units, data-return rules, common recipes, and traps to read before writing CAD scripts.

Instructions

Return the scripting guide for one app: language, predefined names, units, how to return data, common recipes and traps. Read it before scripting an app.

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": {
      "app": "<app>"
    },
    "name": "cad_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds that the payload is static reference documentation and that reading it is a prerequisite, but says nothing about size, per-app variation, or versioning of the guide.

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 sentences, both earning their place: the first front-loads what is returned and its scope, the second delivers the actionable precondition. No filler or repetition of the title.

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?

An output schema exists, so return values need not be described, and the annotations cover safety. The remaining gap is material for such a simple tool: the only input parameter's value space is unexplained anywhere, and the description does not point at cad_apps as the way to resolve a valid app.

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

Parameters2/5

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

Schema description coverage is 0% and there is no enum, so the single 'app' parameter is completely undocumented structurally. The description only implies it selects one app at a time ('for one app') and gives no hint about accepted identifier formats or where to obtain them, leaving the agent to guess.

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?

States a specific verb and resource ('Return the scripting guide for one app') and enumerates the guide's contents (language, predefined names, units, return-data conventions, recipes, traps). This clearly distinguishes it from model-manipulation siblings like cad_modify and cad_read, though no sibling is named explicitly.

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?

The closing imperative 'Read it before scripting an app' gives an explicit precondition for calling it, which is exactly the guidance an agent needs to sequence this tool ahead of script-writing. It stops short of stating when not to use it or pointing to cad_apps for discovering valid app identifiers.

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