Skip to main content
Glama
KyuRish

mcp-dashboards

by KyuRish
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

Bubble Map

render_bubble_map
Read-onlyIdempotent

Generate a geographic bubble map to visualize location-based data. Place sized circles at latitude and longitude coordinates to show city metrics, office sites, or event density.

Instructions

Render a bubble/pin map - sized circles at geographic coordinates. Pass an array of { label, latitude, longitude, value } points. Great for showing city-level data, office locations, event density, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesArray of geographic data points
themeNoTheme preset: boardroom, corporate, sales-floor, golden-treasury, clinical, startup, ops-control, tokyo-midnight, zen-garden, consultant, black-tron, black-elegance, black-matrix, forest-amber, forest-earth, sky-light, sky-ocean, sky-twilight, gray-hf, gray-copilot, office-red
titleYesChart title
effectsNoOverride effects: none, subtle, shimmer, neon, energetic
paletteNoOverride palette only (mix-and-match)
sizeRangeNoMin and max bubble radius in pixels. Default: [3, 25]
projectionNoMap projection. Default: naturalEarth1
typographyNoOverride typography: professional, luxury, cyberpunk, editorial, mono, bold, system, techno
bubbleColorNoBubble fill color. Default: theme accent
showOutlineNoShow country outlines. Default: true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.4.1
    • addedInput schema / properties / sizeRange / additionalItems
      Added value: +false
    • addedInput schema / properties / sizeRange / maxItems
      Added value: +2
    • addedInput schema / properties / sizeRange / minItems
      Added value: +2
  2. Changed1 schema field changedv2.2.0
    • changedInput schema / properties / theme / description
      Previous value: -"Theme preset: boardroom, corporate, sales-floor, golden-treasury, clinical, startup, ops-control, tokyo-midnight, zen-garden, consultant, black-tron, black-elegance, black-matrix, forest-amber, forest-earth, sky-light, sky-ocean, sky-twilight, gray-hf, gray-copilot"New value: +"Theme preset: boardroom, corporate, sales-floor, golden-treasury, clinical, startup, ops-control, tokyo-midnight, zen-garden, consultant, black-tron, black-elegance, black-matrix, forest-amber, forest-earth, sky-light, sky-ocean, sky-twilight, gray-hf, gray-copilot, office-red"
  3. Addedv2.1.0
  4. Removedv1.0.1
  5. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the input shape and the absence of side effects implied by 'render', but says nothing about what is produced or returned (image, HTML, file path), which matters for a no-output-schema render tool.

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?

Three short sentences, front-loaded with the core verb and encoding, then the data contract, then use cases. The middle sentence largely duplicates the schema's array item definition, so it is slightly redundant rather than wasteful.

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 a 10-parameter tool with no output schema, the description covers the essential required input but omits any mention of the many styling parameters (theme, palette, effects, projection, sizeRange) and what the caller receives back. The schema carries parameter detail, but return behavior is left to inference.

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 all ten parameters including defaults are already documented in the schema. The description restates the required point fields ({label, latitude, longitude, value}) but adds no syntax, units, or constraint detail beyond the schema; baseline 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?

States a specific verb and resource ('Render a bubble/pin map - sized circles at geographic coordinates') and even defines the visual encoding, which is more than a tautology. It doesn't explicitly distinguish itself from siblings like render_geo_chart or render_scatter_chart, so an agent must infer the difference.

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

Usage Guidelines3/5

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

The closing sentence gives positive use cases ('city-level data, office locations, event density'), which implies when this tool fits. It gives no exclusions or named alternatives (e.g., when to prefer render_geo_chart or a plain scatter), so routing is only partially guided.

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

Deploy Server

Other Tools