platform_stats
Read-onlyIdempotent
Return public, aggregate LIQAA usage figures (no personal data): registered users, meetings created, and meetings that actually convened.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
meetings
by io.liqaa
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds meaningful context: 'public', 'aggregate', 'no personal data', and specific metrics. No contradictions.
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, front-loaded with key info, no fluff. Every word earns its place.
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 parameterless tool with no output schema, the description fully informs what the tool returns. No gaps evident.
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?
No parameters exist; schema coverage is 100%. Description doesn't need to add param meaning. Baseline 4 for zero-parameter tools.
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?
Description clearly specifies it returns public aggregate LIQAA usage figures, listing three specific metrics (registered users, meetings created, meetings convened). This verb+resource combination is distinct from siblings like create_instant_room or list_plans.
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?
States 'public' and 'no personal data', implying safe usage. Does not explicitly mention when to use vs alternatives, but sibling names provide implicit differentiation. Lacks an explicit when-not or alternative reference.
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.