list_plans
Read-onlyIdempotent
List LIQAA subscription plans with monthly price (DZD) and the maximum participants allowed per meeting.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
meetings
by io.liqaa
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds limited behavioral context by specifying the output fields, but doesn't describe any side effects or other traits.
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?
Single sentence that completely describes the tool's purpose without any unnecessary words.
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?
Given no parameters, rich annotations, and no output schema, the description is mostly complete. It could mention if there are multiple plans or pagination, but for a simple list tool it's sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema is empty, so baseline is 4. The description adds meaning beyond the schema by explaining what the tool returns.
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 clearly states it lists LIQAA subscription plans and specifies the returned fields (monthly price and max participants). This clearly distinguishes it from sibling tools like create_instant_room.
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?
No guidance on when to use this tool versus alternatives. The description only states what the tool does without any usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.1/5.0
Disambiguation5/5
Each tool serves a clear, non-overlapping purpose: creating a room, listing plans, and providing platform capacity and usage statistics. There is no ambiguity in their roles.
Naming Consistency3/5
Two tools follow a verb_noun pattern (create_instant_room, list_plans), but the other two use a noun_verb style (platform_capacity, platform_stats). This mix of conventions reduces consistency.
Tool Count4/5
Four tools feel appropriate for a focused meetings server that emphasizes instant rooms and informational queries. The count is neither too sparse nor overwhelming for the scope.
Completeness3/5
The set covers room creation and basic informational needs, but lacks operations like joining, listing, or managing rooms, leaving gaps for a full meeting lifecycle.