Skip to main content
Glama

Set pin callout

set_callout
Destructive

Add, edit, move, or REMOVE a callout bubble on a pin — a small card floating on the map showing chosen field values (price, acreage, custom fields, …) with a leader line back to the dot. Snippet image exports include these bubbles, so they're how owners show VALUES in a shared picture. Target one pin by compId (preferred) or name — an ambiguous name returns candidates instead of guessing. 'fields' sets what's displayed, in order; omit it to keep the current fields (or smart defaults on a new callout). direction + distanceMiles place the bubble relative to the pin; omit both to leave its position alone. remove:true deletes the pin's callout.

Input Schema

NameRequiredDescriptionDefault
nameNoPin name, case-insensitive. Must resolve to exactly one Point pin.
compIdNoPin ID (preferred — unambiguous)
fieldsNoOrdered field keys/labels to display, e.g. ['price','acreage','pricePerAcre']. Custom field names work too. Only fields that have a value on the pin are shown.
removeNotrue = delete this pin's callout bubble
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
directionNoBubble position relative to the pin: top-right (default for new callouts), top-left, bottom-right, bottom-left, top, bottom, left, right
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
distanceMilesNoHow far from the pin, in miles (default 0.35). Owners can always fine-tune by dragging.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true; the description goes further by specifying exactly what 'remove:true' deletes (the pin's callout) and clarifying that omitted fields/position leave existing state untouched. It doesn't mention permissions or reversibility, but the mutation semantics are disclosed clearly.

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 resource, then moves through targeting, fields, position, and removal. Dense but each clause carries operational information; the mid-sentence parenthetical about what a callout is is the only mild padding.

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 9-parameter mutation tool with no output schema, the description covers the essential behaviors: targeting resolution, field ordering, position defaults, and deletion. Return/candidate format is only lightly touched, but nothing critical for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema: 'fields' is ordered and omit-to-keep behavior, direction+distanceMiles placement semantics, and compId-over-name preference — all go beyond the field-level docs.

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?

States specific verbs (add/edit/move/remove) and a precise resource (a callout bubble on a pin), then defines what that resource is. No sibling tool overlaps this function, so an agent can identify it unambiguously.

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?

Gives clear targeting guidance (compId preferred, ambiguous name returns candidates rather than guessing) and states the effect of omitting 'fields' and position parameters. It stops short of explicit when-not-to-use or routing to an alternative sibling, but the conditional behavior is well covered.

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