Skip to main content
Glama
Sign In

lesgooo.fun

by fun.lesgooo
OverviewDiscussionsAdmin

Create a plan

create_plan

Creates a new saved lesgooo group plan with the user as its first participant. Use when the user wants to start planning something new. Returns the shareable plan links and the participant's private credentials (participant_id, participant_token) needed for later changes. Title and name are optional. Sends no invitations or notifications.

Input Schema

NameRequiredDescriptionDefault
titleNoUser-supplied short plan name (max 120 chars). Omitted when unknown; temporary Event label until collected after the requested action.
your_nameNoUser-supplied participant name (max 80 chars). Omitted when unknown; temporary Organizer participant until their name is collected after the requested action.
request_idNoOptional UUID v4 for atomic creation. An identical UUID and identical fields (including omissions) replay the same creation; a changed payload is rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / request_id / description
      Previous value: -"Optional UUID v4 for an atomic create with your_name. Keep the same UUID and fields on retry; never reuse it for a different plan."New value: +"Optional UUID v4 for atomic creation. An identical UUID and identical fields (including omissions) replay the same creation; a changed payload is rejected."
    • changedInput schema / properties / title / description
      Previous value: -"Short plan name, e.g. \"Weekend at the cabin\" (max 120 chars)."New value: +"User-supplied short plan name (max 120 chars). Omitted when unknown; temporary Event label until collected after the requested action."
    • changedInput schema / properties / your_name / description
      Previous value: -"Name of the person you act for; adds them as the first participant (max 80 chars)."New value: +"User-supplied participant name (max 80 chars). Omitted when unknown; temporary Organizer participant until their name is collected after the requested action."
    • changedInput schema / required
      Previous value: -[
-  "title"
-]New value: +[]
  2. Changed1 schema field changed
    • addedInput schema / properties / request_id
      Added value: +{
+  "description": "Optional UUID v4 for an atomic create with your_name. Keep the same UUID and fields on retry; never reuse it for a different plan.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely useful context beyond that: the return payload (shareable links plus private participant_id/participant_token), the fact that no invitations are sent, and that title/name are optional. The request_id replay semantics live in the schema rather than the description, leaving a small gap.

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?

Five short sentences, zero padding, and the operation and participant scope are front-loaded ahead of the return-value and side-effect notes. Every sentence carries distinct information.

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?

No output schema exists, and the description compensates by naming the return values (shareable links, participant credentials) and flagging the side-effect absence. For a 3-param creation tool with annotations present, nothing critical is missing.

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 coverage is 100%, so the schema already fully documents title, your_name, and request_id, including the UUID replay behavior. The description only reiterates that title and name are optional, adding little meaning beyond the structured fields. Baseline 3 is appropriate.

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 a specific verb and resource ('Creates a new saved lesgooo group plan') plus a distinguishing behavior ('with the user as its first participant'). This clearly separates it from siblings like get_plan, join_plan, and update_event without needing to open their schemas.

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?

Provides a clear trigger condition: 'Use when the user wants to start planning something new.' The note that it 'sends no invitations or notifications' implicitly distinguishes it from join_plan and invite flows, but no sibling is named explicitly and no when-not guidance is given.

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