Lists installed Roku apps and known channel catalog while reporting the TV's current control mode, so you can identify what is available before launching or managing apps.
Lista os aplicativos disponíveis, catálogo de canais conhecidos e informa o modo de controle da TV.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Lista' implies a read-only operation and the mention of reporting the TV control mode adds useful context beyond the name, but there is no disclosure of side effects, permissions, or whether the listing is cached/live.
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 front-loaded sentence with no filler, naming the three things it returns. It is efficient, though the combination of apps, channel catalog and control mode in one clause is slightly dense and could be split for readability.
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?
An output schema exists, so return values need not be explained, and with zero parameters the description only needs to state what is produced. It does that, though the lack of any routing hint toward roku_launch_app leaves a small gap for a tool embedded in a seven-sibling set.
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?
The tool takes zero parameters, so the description has no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misrepresents the empty input schema.
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?
States a specific verb and resource ('Lista os aplicativos disponíveis') and adds two secondary outputs: the known channel catalog and the TV control mode. The purpose is clear, but it never distinguishes itself from siblings like roku_search or roku_launch_app, which plausibly touch the same app catalog.
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?
There is no guidance on when to call this versus roku_search or roku_launch_app, nor any note that this is the natural precursor to launching an app. The usage is only inferable from the tool name, not stated in the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.