tidal_browse_local_genresBrowse localized genre pages for your TIDAL account to explore region-specific genres and discover music that matches your location.
Return the localized genre page.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| item | No | ||
| text | No | ||
| count | No | ||
| items | No | ||
| limit | No | ||
| value | No | ||
| offset | No | ||
| has_more | No | ||
| warnings | No | ||
| operation | Yes | ||
| next_offset | No |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the vague term "localized" without explaining what localization means, whether authentication is required, or how the returned page behaves.
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?
The description is a single front-loaded sentence with no filler. It is concise, though its brevity contributes to the ambiguity rather than resolving it.
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?
Given the many sibling browse tools, the definition is incomplete: it does not explain what a "localized genre page" contains or how it differs from tidal_browse_genres, tidal_list_genres, or tidal_get_genre_items. An output schema exists so return details are not required, but the missing sibling differentiation is a significant gap.
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 no parameters, and the rubric baseline for zero parameters is 4. The schema is empty and no additional parameter meaning is needed.
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?
The description says the tool returns a "localized genre page," giving a verb and resource, but "localized genre page" is vague and is essentially a restatement of the tool name/title. It does not differentiate this tool from siblings like tidal_browse_genres or tidal_list_genres, leaving the agent to guess what makes this page distinct.
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?
The description offers no guidance on when to use this tool versus alternatives such as tidal_browse_genres, tidal_list_genres, or tidal_get_genre_items. There is no explicit context, prerequisite, or exclusion provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.