app.pindropped/pindropped
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINDROPPED_BASE_URL | No | Overrides the PinDropped API host, which is useful for staging. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pinsA | Find live pins on the PinDropped map. Give either lat+lng (+ radius_m, default 1000 m, max 50000; results sorted by distance) or bbox="minLng,minLat,maxLng,maxLat". Optional category filter: one of event, sale, free, lost_found, help, housing, business, notice, fun, other. Each result includes title, body, category, link, expires_at, and a shareable url. |
| get_pinA | Get one PinDropped pin by its id (e.g. '2f2187f85a7c'). Returns full details plus its share url. |
| pin_urlB | Return the public, shareable page URL for a pin id (https://pindropped.app/p/{id}). Pages have link-preview cards. |
| create_pinA | 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).
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
search_pins, get_pin, and create_pin are clearly distinct (list/lookup/create). The only overlap is between get_pin and pin_url, since both take a pin id and get_pin already returns the share url; descriptions explain the difference (full details vs URL only), so confusion is limited but real.
Three tools follow a clean verb_noun pattern (search_pins, get_pin, create_pin) with consistent snake_case. pin_url breaks the pattern as a noun phrase rather than a verb, a minor deviation that is still readable and predictable.
Four tools is small but each covers a distinct step in the pin lifecycle: discover, inspect, share-link, and post. It is at the thin end for a map-posting service, and pin_url could arguably be folded into get_pin, but nothing is redundant enough to feel padded.
Read and create are covered well, but there is no way to update, delete, or cancel a pin, and no way to list the user's own pins or check payment/plan status after checkout. These are notable gaps for a service that charges for permanent pins, though agents can work around them by sharing URLs and re-searching.