Skip to main content
Glama

addGeoJsonPrimitive

Render GeoJSON as Cesium primitives to display large browser datasets on a 3D globe, from a URL, inline data, or stored resource.

Instructions

Render GeoJSON as Cesium primitives for large browser datasets. Returns { success: boolean, data?: unknown, message?: string, error?: string }.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "addGeoJsonPrimitive"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoLayer ID (auto-generated if omitted)
urlNoGeoJSON file URL (mutually exclusive with data)
dataNoGeoJSON object (mutually exclusive with url)
nameNoLayer display name
showNoWhether to show (default true)
flyToNoFly to the loaded geometry (default true)
sessionIdNoTarget browser session ID for multi-browser routing (optional)
resourceIdNoStored GeoJSON resource ID (mutually exclusive with data or url)
blendOptionNoNative opaque/translucent buffer blending mode
allowPickingNoAllow picking (default true, disable for better performance)
pickMetadataNoAdditional pick metadata set before first render; locked afterwards

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
messageNo
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.139.24
    • addedInput schema / properties / blendOption
      Added value: +{
      +  "description": "Native opaque/translucent buffer blending mode",
      +  "enum": [
      +    "opaque",
      +    "translucent"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / flyTo
      Added value: +{
      +  "description": "Fly to the loaded geometry (default true)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / pickMetadata
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Additional pick metadata set before first render; locked afterwards",
      +  "type": "object"
      +}
  2. Changed1 schema field changedv1.139.22
    • addedInput schema / properties / resourceId
      Added value: +{
      +  "description": "Stored GeoJSON resource ID (mutually exclusive with data or url)",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
  3. Changed1 schema field changedv1.139.19
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "data": {},
      +    "error": {
      +      "type": "string"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "success"
      +  ],
      +  "type": "object"
      +}
  4. Changed2 schema fields changedv1.139.18
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / data / additionalProperties
      Removed value: -{}
  5. Changed8 schema fields changedv1.139.17
    • addedInput schema / properties / data / additionalProperties
      Added value: +{}
    • addedInput schema / properties / data / type
      Added value: +"object"
    • addedInput schema / properties / id / maxLength
      Added value: +200
    • addedInput schema / properties / id / minLength
      Added value: +1
    • addedInput schema / properties / name / maxLength
      Added value: +200
    • addedInput schema / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / url / maxLength
      Added value: +4096
    • addedInput schema / properties / url / minLength
      Added value: +1
  6. Addedv1.139.15

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write with no open-world access, so the safety profile is covered elsewhere. The description adds only the performance framing for large datasets and restates the return envelope; it says nothing about what state the layer persists in, what happens on repeated calls with the same id, or how errors surface.

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?

Two short sentences with the core purpose front-loaded, which is the right shape. The second sentence spends space on a return shape that the output schema already defines, so it does not fully earn its place.

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

Completeness3/5

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

For an 11-parameter mutation tool with nested objects and an output schema, the description is thin: the output schema excuses the return-value sentence, but nothing explains layer lifecycle or the critical distinction from addGeoJsonLayer. It is callable from the schema alone, but not confidently selectable over its sibling.

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 every one of the 11 parameters — including the mutually exclusive id/url/data/resourceId trio and the blendOption enum — is already documented in the schema. The description adds no parameter-level meaning beyond the 'large datasets' hint, so the baseline of 3 applies.

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 gives a specific verb and resource — 'Render GeoJSON as Cesium primitives' — which tells an agent exactly what the call produces. It even scopes it ('for large browser datasets'), but it never distinguishes itself from the near-identical sibling addGeoJsonLayer, which is the single biggest ambiguity an agent faces here.

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 only usage signal is the fragment 'for large browser datasets', which hints at a performance-oriented use case but states no thresholds, prerequisites, or exclusions. Critically, with a sibling literally named addGeoJsonLayer, the description offers no rule for choosing between them, leaving the agent to guess.

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