Skip to main content
Glama
mcp-server-shieldtv
by SDNick484

List launchable apps

shield_list_apps
Read-only

Lists valid app names that shield_launch_app accepts, mapping friendly names to the links they open so you can discover the correct name before launching.

Instructions

List the app names launch_app accepts (friendly name -> the link it opens).

<use_case> Discover valid app names for use with shield_launch_app. </use_case>

<important_notes>

  • Returns mapped friendly names from configuration. </important_notes>

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": "shield_list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that it returns mapped friendly names from configuration, which is useful behavioral context beyond the annotations, though it doesn't discuss ordering or completeness of the list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose in the first sentence, and the structured use_case/notes blocks are easy to scan. There is mild redundancy between the opening line and the use_case block, but nothing wasteful.

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?

With an output schema present, the description needn't explain return values, and it correctly focuses on purpose and usage. For a simple zero-param list tool this is essentially complete, with only minor room to note list ordering or freshness.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The parenthetical about friendly name to link mapping adds a bit of meaning about the output shape.

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?

States a specific verb and resource ('List the app names') and immediately scopes it to what launch_app accepts, which cleanly distinguishes it from the sibling shield_launch_app. The parenthetical clarifies the returned mapping, so an agent knows exactly what this produces.

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?

The <use_case> block explicitly says to discover valid app names for use with shield_launch_app, giving clear when-to-use guidance tied to a named sibling. It stops short of stating exclusions or when-not-to-use, but for a zero-param discovery tool the context is sufficient.

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