lms-mcp

get_decades

Read-only

Retrieve the list of decades present in the music library. Use this to filter or browse music by decade.

Instructions

Get decades available in the music library

Tool call template

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_decades"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results (default: 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds no further behavioral details (e.g., return format, sorting, or any side effects). Since annotations cover the safety profile, a 3 is appropriate as the description adds marginal value beyond that.

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 a single, front-loaded sentence with no unnecessary words. It is perfectly concise and earns its place.

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 simple read-only listing tool with one optional parameter and no output schema, the description is mostly complete. It could mention the output format or sorting order, but the information provided is sufficient for an agent to understand the tool's basic function. The presence of readOnlyHint reduces the need for extensive behavioral details.

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% for the single 'limit' parameter, which already includes a default value and brief description. The tool description does not add any additional information about the parameter, so baseline 3 is correct.

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 'Get' and the resource 'decades available in the music library', making the purpose obvious. However, it does not explicitly distinguish from sibling tools like 'get_years', which could cause confusion in selection, though the distinct resource name provides implicit differentiation.

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 explicit guidance on when to use this tool versus alternatives like 'get_years' is provided. The description simply states what it does, leaving the agent to infer usage context without any exclusions or recommendations.

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