Skip to main content
Glama
Sign In

QuintaDB

by ua.com.quintadb
OverviewDiscussionsAdmin

update_map

Idempotent

Change a map: its name, where it is centred (center_type 1 = an address, 2 = coordinates, 3 = the first record) and its zoom. Pass only what changes. add_data_sources adds sources of markers and remove_data_source_ids removes sources by the ids list_maps shows (798); every other source stays as it is. Ids come from list_maps.

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": {
      "app_id": "<app_id>",
      "map_id": "<map_id>"
    },
    "name": "update_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoomNo
app_idYesProject ID (from list_projects)
map_idYes
new_nameNo
center_typeNo1 = an address, 2 = coordinates, 3 = the first record
center_addressNo
center_latitudeNo
add_data_sourcesNoSources of markers to ADD to the ones the map has. Each needs address_field_id, or latitude_field_id with longitude_field_id.
center_longitudeNo
remove_data_source_idsNoIds of the sources to remove, from list_maps

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / add_data_sources
      Added value: +{
+  "description": "Sources of markers to ADD to the ones the map has. Each needs address_field_id, or latitude_field_id with longitude_field_id.",
+  "items": {
+    "properties": {
+      "address_field_id": {
+        "description": "The field with the address (id or name)",
+        "type": "string"
+      },
+      "entity_id": {
+        "description": "The table's id or name",
+        "type": "string"
+      },
+      "info_window": {
+        "description": "Fixed popup text",
+        "type": "string"
+      },
+      "info_window_field_id": {
+        "description": "The field shown in the marker's popup",
+        "type": "string"
+      },
+      "info_window_type": {
+        "description": "1 = from a field, 2 = fixed text",
+        "type": "integer"
+      },
+      "latitude_field_id": {
+        "type": "string"
+      },
+      "longitude_field_id": {
+        "type": "string"
+      },
+      "marker_field_type": {
+        "description": "1 = address, 2 = coordinates",
+        "type": "integer"
+      },
+      "marker_title_field_id": {
+        "description": "The field shown as the marker's title",
+        "type": "string"
+      },
+      "marker_title_type": {
+        "description": "1 = from a field, 2 = fixed text",
+        "type": "integer"
+      },
+      "report_id": {
+        "description": "Instead of entity_id: a report's id, to show only its records",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / remove_data_source_ids
      Added value: +{
+  "description": "Ids of the sources to remove, from list_maps",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare idempotent=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail: sources are added/removed incrementally and 'every other source stays as it is', which tells the agent this is not a wholesale replacement.

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-loaded with the action and the mutable fields, and the add/remove rule follows immediately. Slightly redundant in re-stating the center_type enum that the schema already carries.

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?

For a 10-parameter mutation tool with no output schema and annotations covering the safety profile, the description covers the important non-obvious behaviour (incremental source changes, partial updates, id provenance). Missing only edge details such as default zoom behaviour.

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 only 40%, so the description should compensate. It restates center_type (already documented in the schema) and clarifies the add/remove source semantics, but leaves new_name, zoom, center_address, center_latitude and center_longitude unexplained beyond their names. Partial compensation only.

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 opens with a specific verb+resource ('Change a map') and enumerates exactly what can be changed (name, centring, zoom, data sources). It is readily distinguishable from create_map, delete_map and list_maps, and names list_maps as the id source.

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?

It gives a clear usage rule for this partial-update tool ('Pass only what changes') and points to list_maps for ids. It does not explicitly contrast itself with sibling update_* tools, but the context is unambiguous.

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

All QuintaDB toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources