Skip to main content
Glama

apps

Lists running applications or finds installed and running programs by partial name so you can locate a specific application.

Instructions

List running apps, or find running and installed apps by name.

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

Input Schema

NameRequiredDescriptionDefault
queryNoPart of an app name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the entire burden. It does disclose one genuinely non-obvious behavior — that a name search reaches installed apps, not just running ones — but says nothing about required permissions, whether results are truncated, or what the returned entries contain (e.g., identifiers usable by other tools).

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?

A single sentence, front-loaded with the primary behavior and immediately followed by the filtered variant. Every word carries information; nothing is redundant.

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 one-optional-parameter enumeration tool this covers both call modes adequately. The remaining gap is the shape of returned items, which matters here because there is no output schema and an agent cannot tell what it will receive to feed into sibling tools.

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?

Schema coverage is 100% and the schema already defines query as "Part of an app name", so the baseline is 3. The description goes beyond that by clarifying that query switches the search scope to include installed apps and that omitting it restricts results to running apps, which is real added meaning.

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 names a specific verb and resource ("List running apps") and adds a second mode ("find running and installed apps by name"), so an agent knows exactly what the tool returns. It does not explicitly distinguish itself from the desktop-control siblings (act, observe, see), but none of those names suggest overlapping enumeration behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through the two phrasings: call with no argument to enumerate running apps, or supply a name fragment to search. There is no explicit statement of when to prefer this over a sibling or any precondition (e.g., permissions, platform support).

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

Deploy Server

Other Tools