Skip to main content
Glama

Installed applications

installed_apps
Read-onlyIdempotent

Use this when the user needs to answer what software/packages are installed and their versions. Prefer a filter when looking for one product instead of returning the full inventory.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "device": "<device>"
    },
    "name": "installed_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results; default 1000.
deviceYesReMCP device id returned by list_devices. Required for every device operation.
filterNoName substring.
refreshNoForce native inventory refresh instead of a cached snapshot.

Output Schema

NameRequiredDescriptionDefault
dataNoInstalled applications structured result for installed_apps. Stable fields are declared explicitly; platform-specific fields may be added. Large results may return truncated/bytes/preview instead of the full payload.
textYesConcise human-readable result of the tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / refresh
      Added value: +{
      +  "description": "Force native inventory refresh instead of a cached snapshot.",
      +  "type": "boolean"
      +}
  2. Added
  3. Removed
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the implication that unfiltered results can be very large, which is genuine context, but it does not mention the required device scoping or the cache-versus-refresh behavior beyond what the schema already documents.

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?

Two short sentences with no filler, and the purpose clause is front-loaded ahead of the filter tip. The phrasing 'needs to answer what software/packages are installed' is slightly roundabout where a direct verb would read better.

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?

The tool is simple, has an output schema, full schema coverage and rich annotations, so the description does not need to explain return values or safety. What remains missing is sibling differentiation and any mention of the mandatory device scoping, which limits it just short of complete.

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%, so limit, device, filter and refresh are already explained in structured form, which sets the baseline at 3. The description's filter guidance mildly reinforces how to use that parameter but adds no syntax or selection detail beyond the schema.

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 the resource (software/packages) and the data returned (installed status and versions), so an agent knows this is an inventory-listing tool. It stops short of a crisp verb-plus-resource framing and never distinguishes itself from the similarly named app_catalog sibling.

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?

It gives a real usage condition ('when the user needs to answer what software/packages are installed') and a tactical hint to filter for a single product rather than pull the full inventory. However, it offers no when-not guidance and no routing to any alternative tool, so the agent must infer which sibling to pick.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources