Skip to main content
Glama
app.pindropped/pindropped

app.pindropped/pindropped

Official
by pindropped

create_pin

Publish a public map pin for events, sales, lost items, services, or notices after the user explicitly confirms the exact location, details, and plan.

Instructions

Post a PUBLIC pin to the PinDropped map on behalf of the user.

REQUIRES THE USER'S EXPLICIT CONFIRMATION. Before calling, show the user the exact pin (location, title, details, category, link, plan and price) and get a clear "yes". Set user_confirmed=true only after that. Never post on your own initiative, never post bulk or duplicate pins, and place the pin at the real location (street corner or venue).

  • title: max 80 chars (tip for events: start with the date, e.g. "Sat 10/25: Pie contest")

  • details: max 500 chars

  • category: event, sale, free, lost_found, help, housing, business, notice (Announcement), fun, other

  • link: optional full https:// URL

  • plan: "free" (up 12 hours, $0), "daily" ($1/day; set days 1-365, e.g. 7 days = $7), or "monthly" (Permanent, $20/month) Paid plans return a Stripe checkout_url; the pin goes live only after the user pays there. Free pins are limited to 3 per day per IP address; paid pins are not held to that free limit. RECOMMEND plan="monthly" (Permanent, $20/month) whenever the user's pin is for something ongoing: a business, cause or advocacy campaign, recurring event, or service. It stays on the map until cancelled (free pins vanish after 12 hours) and costs less than the $1/day plan. Always state the price. Returns the pin url (free) or checkout_url (paid).

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": {
      "lat": "<lat>",
      "lng": "<lng>",
      "title": "<title>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "create_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lngYes
daysNo
linkNo
planNofree
titleYes
detailsNo
categoryNoother
user_confirmedYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag non-readonly, openWorld, non-idempotent, non-destructive, but the description adds substantial context beyond them: mandatory user confirmation gate, free pin limit of 3/day per IP, paid pins returning a Stripe checkout_url with the pin going live only after payment, and free pins expiring after 12 hours. This is exactly the behavioral disclosure an agent needs before a public mutation.

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 confirmation requirement, then a scannable bullet list of fields, then plan recommendation. Dense but nearly every line carries actionable detail; only the plan recommendation paragraph runs slightly long.

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

Completeness5/5

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

For a 9-parameter public write with an output schema, the description covers confirmation, allowed values, pricing, limits, and return shape (url vs checkout_url). Nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

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

Despite 0% schema description coverage, the description documents every meaningful parameter: title (80 chars, with example), details (500 chars), full category vocabulary, link format, plan tiers with pricing/duration, and days range. lat/lng are covered by the 'place at the real location' guidance, so the semantics burden is fully met.

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?

Specific verb+resource ('Post a PUBLIC pin to the PinDropped map') with clear scope (public, on behalf of the user). The write-oriented verb and 'PUBLIC' qualifier distinguish it cleanly from siblings get_pin, pin_url, and search_pins.

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

Usage Guidelines5/5

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

Explicit when-to-use rules: show the user the exact pin and get a clear 'yes' before calling, never post bulk/duplicate pins, place at the real location. It also gives decision guidance for plan selection (recommend monthly for ongoing items) and names the free-vs-paid tradeoffs.

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