Skip to main content
Glama

upload_terrain_base64

Upload terrain/CAD/GIS (.dxf/.tif/.asc/.las/.geojson/.csv/.zip) as base64 or text.

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": {
      "filename": "<filename>"
    },
    "name": "upload_terrain_base64"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
upload_idNo
content_textNo
content_base64No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses that uploads can be base64 or text and lists supported formats, but omits permissions, size limits, persistence, validation behavior, and what the tool returns.

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?

The definition is a single front-loaded sentence with zero redundant wording. It communicates the core action and supported formats efficiently.

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 four-parameter upload tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. An agent still lacks essential details about parameter usage, content-field selection, upload_id semantics, and constraints.

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 must explain all four parameters. It implies the base64/text choice for content_base64/content_text and links formats to filename, but does not explain upload_id, required filename, or mutual exclusivity between content fields.

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 uses a specific verb (Upload) and resource category (terrain/CAD/GIS), and lists concrete supported formats. It is clear what the tool does, though it does not explicitly differentiate itself from sibling simulation tools.

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?

The description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. Usage is only implied by the terrain/CAD/GIS file formats.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources