Skip to main content
Glama

create_simul

Create a simultaneous exhibition on Lichess to play multiple opponents at once, configuring game settings like time controls, rating limits, and variant.

Instructions

Create a new simul

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the simul
variantNoVariant keystandard
clockTimeNoClock initial time in minutes
clockIncrementNoClock increment in seconds
minRatingNoMinimum rating to join
maxRatingNoMaximum rating to join
colorNoColor the host will playwhite
textNoDescription of the simul
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create a new simul' implies a write/mutation operation but doesn't disclose permissions needed, whether this requires authentication, what happens on success/failure, rate limits, or side effects. For a creation tool with zero annotation coverage, this is insufficient behavioral context.

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 extremely concise at just three words. It's front-loaded with the essential action and resource. There's zero wasted language or unnecessary elaboration. This represents optimal conciseness for a tool description.

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

Completeness2/5

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

For a creation tool with 8 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what a 'simul' is (simultaneous exhibition in chess), what happens after creation, return values, or error conditions. The agent lacks sufficient context to use this tool effectively despite the comprehensive parameter schema.

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%, so all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the schema. According to guidelines, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description.

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?

The description clearly states the verb 'create' and the resource 'simul', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'create_arena', 'create_challenge', or 'create_swiss' which also create different types of events. The description is specific about what's being created but lacks sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'create_arena' or 'create_challenge'. There's no mention of prerequisites, appropriate contexts, or exclusions. The agent must infer usage from the tool name alone without any explicit guidelines.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/karayaman/lichess-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server