Skip to main content
Glama
Sign In

Aspicio

by io.github.frontsail-ai
OverviewDiscussionsAdmin

Load a DXF for the viewer widget

load_dxf_for_viewer
Read-only

Internal: returns DXF bytes (base64) for the in-chat viewer. Called by the widget, not the model.

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

Input Schema

NameRequiredDescriptionDefault
lengthNoByte length of the requested range
offsetNoByte offset of the requested range
sourceYeshttp(s) URL of the drawing (same guards as the other tools)

Output Schema

NameRequiredDescriptionDefault
offsetYesByte offset this slice starts at
byteLengthYesTotal size of the whole file
bytesBase64YesThe requested bytes, base64

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / source / description
      Previous value: -"http(s) URL of the DXF (same guards as the other tools)"New value: +"http(s) URL of the drawing (same guards as the other tools)"
    • addedOutput schema / properties / bytesBase64
      Added value: +{
+  "description": "The requested bytes, base64",
+  "type": "string"
+}
    • removedOutput schema / properties / dxfBase64
      Removed value: -{
-  "description": "The requested bytes, base64",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "dxfBase64",
-  "byteLength",
-  "offset"
-]New value: +[
+  "bytesBase64",
+  "byteLength",
+  "offset"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "byteLength": {
+      "description": "Total size of the whole file",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "dxfBase64": {
+      "description": "The requested bytes, base64",
+      "type": "string"
+    },
+    "offset": {
+      "description": "Byte offset this slice starts at",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "dxfBase64",
+    "byteLength",
+    "offset"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, and destructiveHint. The description adds context that it returns base64 bytes and is internal, but no additional behavioral details beyond what annotations imply.

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, front-loaded with the main purpose, and no wasted words.

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?

Given that output schema exists and parameters are fully documented in schema, the description provides sufficient context for an internal tool. It lacks only minor details like response format or error handling.

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 description coverage is 100%, so the description does not add any meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool returns DXF bytes (base64) for the in-chat viewer, and distinguishes it from siblings by specifying it is internal and called by the widget.

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 description explicitly says 'Called by the widget, not the model,' which guides the agent not to invoke it directly. However, it does not discuss alternatives or specific conditions.

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

All Aspicio toolsInspect
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.

Resources