Skip to main content
Glama
Sign In
jwmcp

jwmcp

by Koheui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

jww_to_dxf

Convert .jww CAD drawings to DXF (AC1024 by default) using ezjww and return the output file path.

Instructions

Convert a .jww to DXF (AC1024 by default) using ezjww. Returns the output path.

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": {
      "path": "<path>"
    },
    "name": "jww_to_dxf"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNo
pathYes
versionNoAC1024

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool returns the output path, but does not cover permissions, whether it overwrites files, error conditions, or side effects. The mention of 'using ezjww' is implementation detail, not behavioral context an agent needs for invocation.

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?

The description is a single efficient sentence that front-loads the conversion action and mentions the default. It is concise, though it could be slightly more informative without being verbose.

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

Completeness2/5

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

For a 3-parameter conversion tool with no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It should clarify parameter roles, return behavior, and any prerequisites. The current description leaves significant gaps for correct invocation.

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%, so the description should compensate but does not. It mentions a default version 'AC1024' but does not explain the 'path' parameter (input file path) or 'out' parameter (output file path). An agent cannot infer the meaning of these parameters from the description alone.

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+resource: 'Convert a .jww to DXF.' It also mentions the default output version and the library used, which distinguishes it from sibling tools like drawing_import_jww or jww_info. This is clear and actionable.

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 explicit guidance on when to use this tool versus alternatives such as drawing_import_jww or drawing_export. The description only states what it does, not the context or prerequisites for choosing it.

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