Skip to main content
Glama
Sign In

lesgooo.fun

by fun.lesgooo
OverviewDiscussionsAdmin

lesgooo planner

open_planner
Read-only

Opens the interactive lesgooo planner (When, Where, Event, Checklist, Splitwise) in the conversation, optionally on a saved plan and module and as a previously selected participant. Without a plan it shows an unsaved local draft. Opening saves nothing. Use when the user wants to see or edit the plan visually.

Input Schema

NameRequiredDescriptionDefault
planNo
moduleNo
participant_idNoPreviously selected participant in this plan; requires participant_token.
participant_tokenNoToken returned by join_plan/create_plan for this participant and plan; requires participant_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / participant_id
      Added value: +{
+  "description": "Previously selected participant in this plan; requires participant_token.",
+  "type": "string"
+}
    • addedInput schema / properties / participant_token
      Added value: +{
+  "description": "Token returned by join_plan/create_plan for this participant and plan; requires participant_id.",
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly annotation, the description adds useful behavior: opening saves nothing, and without a plan it shows an unsaved local draft. It does not describe participant-token requirements, but those are partly covered in the schema.

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?

The description is front-loaded, compact, and every sentence contributes: purpose, optional targeting, draft behavior, no-save behavior, and usage trigger. There is no repetition or filler.

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

Completeness4/5

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

For a read-only interactive opener with no output schema, the description covers what the tool does, what happens with no plan, and when to use it. Minor gaps remain around participant-token coupling and exact return/UI behavior.

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?

The description adds useful optionality context for plan, module, and participant selection. However, with only 50% schema description coverage, it does not fully compensate for the token-pairing requirements or module value mapping.

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?

The description states a specific verb and resource: opens the interactive lesgooo planner in the conversation. It also names the planner modules and distinguishes the tool from plan-mutating siblings by emphasizing that opening saves nothing.

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?

It gives a clear usage condition: use when the user wants to see or edit the plan visually. It does not explicitly name alternatives such as get_plan or create_plan, but the intended context is clear.

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