Retrieve a list of all players connected to the Lyrion Music Server.
Get all available players from the LMS server
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_players"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the description's behavioral burden is lowered. The description adds no extra behavioral context beyond what the annotation implies (e.g., no mention of performance, resource impact, or return format). It is consistent but does not enrich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, short sentence that conveys the entire purpose without any wasted words. Front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, parameterless retrieval tool, the description is nearly complete. It lacks details about what the returned players contain (e.g., IDs, names), but given the absence of an output schema, the description still serves its primary goal of identifying what the tool does.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, and the description states 'all available players', which clarifies the scope. With no parameters and 100% schema coverage, the description adds sufficient meaning—it confirms no filtering is possible.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action (Get) and the resource (all available players from the LMS server). The verb+resource combination is specific and distinct from sibling tools like get_player_status or sync_players, which imply different scopes or actions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or when-not-to-use guidance is provided. However, the tool's simplicity (no parameters, retrieving all players) makes its usage obvious. It implicitly contrasts with siblings that operate on specific players, but no alternatives are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.