Aspicio

Describe a drawing of any supported format

describe_doc

Read-only

Return a structured JSON summary of a drawing in any supported format (DXF or PDF), detected from its bytes rather than its name. Use this when you do not know which format you have; the reply names the format that was read. Covers the whole drawing by default, including every page of a multi-page PDF; pass space (a name from the reply's spaces) to scope it to one page or sheet. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render.

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": {
      "source": "<source>"
    },
    "name": "describe_doc"
  }
}

Input Schema

Name	Required	Description	Default
`space`	No	Which space to work on: "Model" (a PDF's page 1, a DXF's model space) or a page/layout name as listed in a describe reply's "spaces". Describe omits it for the whole drawing; render defaults to the first space.
`source`	Yes	A publicly reachable http(s) URL, or inline DXF text. A PDF is binary, so it must be a URL — inline PDF bytes are refused. (This is a hosted server — local file paths are not available; use the npx @aspicio/mcp local server for files on disk.)

Output Schema

Name	Required	Description
`size`	Yes	Bounding-box size in drawing units, null when empty
`space`	Yes	Which space this summary is scoped to, or null when it covers the whole drawing (bounds/size then describe spaces[0], the space render returns)
`texts`	Yes	Unique TEXT/MTEXT strings, blocks included
`units`	Yes	Drawing-unit label (e.g. "mm"), "" when unitless
`bounds`	Yes	World-space extents, null for an empty drawing
`format`	Yes	Which format was read ("dxf", "pdf")
`layers`	Yes
`spaces`	Yes	Every space in the drawing (a PDF's pages, a DXF's model space and layouts), model space first. These do not sum to entityCount: a DXF sheet's viewports re-show model geometry, so an entity can be drawn in two spaces while existing once
`entityCount`	Yes
`entityTypes`	Yes	Top-level entities per DXF type
`unsupported`	Yes	Per-kind counts of what was skipped
`segmentCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026
- removedOutput schema / properties / space / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / space / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed4 schema fields changedAug 10, 2026

addedInput schema / properties / space

Added value: +{
+  "description": "Which space to work on: \"Model\" (a PDF's page 1, a DXF's model space) or a page/layout name as listed in a describe reply's \"spaces\". Describe omits it for the whole drawing; render defaults to the first space.",
+  "type": "string"
+}

addedOutput schema / properties / space

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Which space this summary is scoped to, or null when it covers the whole drawing (bounds/size then describe spaces[0], the space render returns)"
+}

addedOutput schema / properties / spaces

Added value: +{
+  "description": "Every space in the drawing (a PDF's pages, a DXF's model space and layouts), model space first. These do not sum to entityCount: a DXF sheet's viewports re-show model geometry, so an entity can be drawn in two spaces while existing once",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "bounds": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "maxX": {
+                "type": "number"
+              },
+              "maxY": {
+                "type": "number"
+              },
+              "minX": {
+                "type": "number"
+              },
+              "minY": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "minX",
+              "minY",
+              "maxX",
+              "maxY"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "entityCount": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "name": {
+        "description": "Pass as `space` to scope a describe or render to it",
+        "type": "string"
+      },
+      "segmentCount": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "size": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "height": {
+                "type": "number"
+              },
+              "width": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "width",
+              "height"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "name",
+      "entityCount",
+      "segmentCount",
+      "bounds",
+      "size"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "format",
-  "units",
-  "bounds",
-  "size",
-  "entityCount",
-  "segmentCount",
-  "layers",
-  "entityTypes",
-  "unsupported",
-  "texts"
-]New value: +[
+  "format",
+  "units",
+  "bounds",
+  "size",
+  "space",
+  "entityCount",
+  "segmentCount",
+  "spaces",
+  "layers",
+  "entityTypes",
+  "unsupported",
+  "texts"
+]

Changed1 schema field changedJul 30, 2026

changedInput schema / properties / source / description

Previous value: -"A publicly reachable http(s) URL to a .dxf file, or the DXF content inline as text. (This is a hosted server — local file paths are not available; use the npx @aspicio/mcp local server for files on disk.)"New value: +"A publicly reachable http(s) URL, or inline DXF text. A PDF is binary, so it must be a URL — inline PDF bytes are refused. (This is a hosted server — local file paths are not available; use the npx @aspicio/mcp local server for files on disk.)"

AddedJul 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds real behavior beyond the readOnly/non-destructive annotations: default scope is the entire drawing including every page of a multi-page PDF, and the reply names the format that was read. It does not address failure modes, size limits, or cost, so it stops short of fully complete behavioral disclosure.

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?

Front-loads the purpose and format-detection rationale, then layers scope and the sibling alternative. The final sentence about platform gating is long and somewhat conditional, but it still earns its place by preventing a wrong substitution.

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

Completeness5/5

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

With annotations carrying the safety profile and an output schema carrying return shape, the description only needs to cover purpose, scope defaults, and sibling routing — and it does all three. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so both parameters are already documented in detail. The description's explanation of `space` ('a name from the reply's spaces', omitting it covers the whole drawing) largely restates what the schema's parameter descriptions already say, so it adds little beyond the baseline.

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?

States a specific verb and resource ('Return a structured JSON summary of a drawing') plus the key differentiator: format detected from bytes rather than name, covering both DXF and PDF. This immediately distinguishes it from the format-specific siblings describe_dxf and describe_pdf.

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

Usage Guidelines5/5

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

Gives an explicit selection rule ('Use this when you do not know which format you have'), names the alternative (view_dxf) with the condition that selects it (user wants to explore visually), and even handles the approval-gating edge case. This is the when/when-not/alternatives triad in full.

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

All Aspicio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.