Skip to main content
Glama
Sign In

lesgooo.fun

by fun.lesgooo
OverviewDiscussionsAdmin

Suggest a place

add_place
Idempotent

Suggests a place for the group to vote on (Where). By default it searches Google Places and returns up to five candidates without saving (status needs_selection); calling it again with the chosen google_place_id saves the place with its official details, map link and photo. source=manual saves a supplied name, address or link without a lookup. Duplicates are merged. Use when the user proposes a venue or destination.

Input Schema

NameRequiredDescriptionDefault
linkNoOptional link to any other page about the place (http/https), instead of google_maps_url.
nameYesRequested place name, including accents (max 300 chars). A selected Google result supplies its official name.
planYesSaved plan link (e.g. https://lesgooo.fun/ab12/when) or its 4-character plan ID. Links without a plan ID (e.g. https://lesgooo.fun/when) are unsaved local drafts and are not accepted.
queryNoOptional Google autocomplete query including the known city/address (max 160 chars); otherwise name/address are used.
sourceNoDefault auto uses Google first. Manual explicitly saves the supplied name/address/link without a paid lookup.
addressNoOptional address (max 500 chars).
participant_idYesFrom create_plan or join_plan.
google_maps_urlNoOptional Google Maps link (google.com/maps or maps.app.goo.gl). Links with coordinates (…/@50.08,14.42,…) also show a map preview.
google_place_idNoExact place ID from returned Google candidates; official details are loaded server-side (max 160 chars).
participant_tokenYesFrom create_plan or join_plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / plan / description
      Previous value: -"Saved plan link (e.g. https://lesgooo.fun/ab12/when) or its 4-character id. Bare module links such as https://lesgooo.fun/when are local drafts: ask for a saved link, never substitute a previous plan ID."New value: +"Saved plan link (e.g. https://lesgooo.fun/ab12/when) or its 4-character plan ID. Links without a plan ID (e.g. https://lesgooo.fun/when) are unsaved local drafts and are not accepted."
  2. Changed4 schema fields changed
    • addedInput schema / properties / google_place_id
      Added value: +{
+  "description": "Exact place ID from returned Google candidates; official details are loaded server-side (max 160 chars).",
+  "type": "string"
+}
    • changedInput schema / properties / name / description
      Previous value: -"Place name exactly as supplied, including accents (max 300 chars)."New value: +"Requested place name, including accents (max 300 chars). A selected Google result supplies its official name."
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Optional Google autocomplete query including the known city/address (max 160 chars); otherwise name/address are used.",
+  "type": "string"
+}
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Default auto uses Google first. Manual explicitly saves the supplied name/address/link without a paid lookup.",
+  "enum": [
+    "auto",
+    "manual"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Place name (max 300 chars)."New value: +"Place name exactly as supplied, including accents (max 300 chars)."
  4. Changed1 schema field changed
    • changedInput schema / properties / plan / description
      Previous value: -"Plan link (e.g. https://lesgooo.fun/ab12/when) or its 4-character id."New value: +"Saved plan link (e.g. https://lesgooo.fun/ab12/when) or its 4-character id. Bare module links such as https://lesgooo.fun/when are local drafts: ask for a saved link, never substitute a previous plan ID."
  5. Changed2 schema fields changed
    • changedInput schema / properties / google_maps_url / description
      Previous value: -"Optional Google Maps link (google.com/maps or maps.app.goo.gl)."New value: +"Optional Google Maps link (google.com/maps or maps.app.goo.gl). Links with coordinates (…/@50.08,14.42,…) also show a map preview."
    • addedInput schema / properties / link
      Added value: +{
+  "description": "Optional link to any other page about the place (http/https), instead of google_maps_url.",
+  "type": "string"
+}
  6. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover mutation, open-world behavior, idempotency and non-destructiveness. The description adds valuable workflow detail: the default search returns up to five unsaved candidates with status needs_selection, a second call with google_place_id saves official details/map link/photo, manual mode bypasses lookup, and duplicates are merged.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the core behavior and then the main branches (default search, save with google_place_id, manual mode, duplicate merging). Every sentence adds useful information with no padding.

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 10-parameter open-world mutation with no output schema, the description explains what is returned during search, the needs_selection status, and what gets saved after selection. Remaining auth and parameter details are handled by the schema and annotations, so an agent has enough to call it correctly.

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%, and the schema already documents all 10 parameters. The description reinforces the roles of google_place_id and source=manual, but does not add syntax or format details beyond the schema and leaves plan, participant_id, participant_token and query specifics to the schema.

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 ('Suggests a place') plus scope ('for the group to vote on (Where)') and the search-vs-save workflow. It does not explicitly name the sibling vote_place, so sibling differentiation is implied rather than stated.

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 a clear trigger ('Use when the user proposes a venue or destination') and explains when to use source=manual versus the default Google lookup. It does not state when not to use the tool or name vote_place as the alternative for voting.

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

All lesgooo.fun toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources