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
create_pin (write), search_pins (discovery) and get_pin (fetch by id) are clearly distinct. get_pin and pin_url both take a pin id and return URL-ish output, so an agent could reasonably pick either; the overlap is mitigated by pin_url being a lightweight URL builder, but the boundary is soft.
Three of four tools follow a clear verb_noun pattern (get_pin, create_pin, search_pins). pin_url deviates as a bare noun phrase and would be more consistent as get_pin_url, but the set is still highly readable.
Four tools is a tight, well-scoped surface for a pin map service: read one, write one, search, and build a share link. Slightly lean, but nothing feels gratuitous or missing at the count level.
Create, read, and search are covered, but there is no update_pin or delete_pin, so users cannot edit or remove a pin once posted, and there is no way to check a paid pin's payment/status after checkout. These are notable lifecycle gaps for a user-generated content service.