Skip to main content
Glama
Sign In
mech-cad-design-mcp

mech-cad-design-mcp

by bloodreaper005
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

design_knowledge_retrieve

Fetch applicable design knowledge and standards for a CAD design without gating progress. Query by design ID to get needed information.

Instructions

Retrieve applicable knowledge without making retrieval a CAD gate.

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": {
      "design_id": "<design_id>",
      "query": "<query>"
    },
    "name": "design_knowledge_retrieve"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
requiredNo
design_idYes
features_jsonNo{}
used_knowledge_ids_jsonNo[]

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only hints at a possible non-blocking intent with 'without making retrieval a CAD gate,' but it does not disclose side effects, retrieval scope, response behavior, or operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, with no redundant filler. However, it is more under-specified than usefully concise, and the CAD-gate phrase adds ambiguity rather than structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, 0% parameter coverage, and 5 parameters including two required fields, this one-line description is severely incomplete. It does not explain how an agent should construct a query, what the required inputs mean, or what response behavior to expect.

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

Parameters1/5

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

Schema description coverage is 0% with 5 parameters, and the description mentions none of them. The agent is left without any explanation of design_id, query, required, features_json, or used_knowledge_ids_json.

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 states a clear verb and resource: 'Retrieve applicable knowledge.' It is specific enough to convey the basic action, though it does not explicitly distinguish this tool from its siblings, and the phrase 'without making retrieval a CAD gate' is somewhat jargon-heavy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool instead of siblings such as design_status, design_record_result, or design_lesson_decide. There are no conditions, exclusions, or alternative tool references.

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