Skip to main content
Glama

List or search app-center apps

nas_app_list
Read-only

Lists NAS app center apps or searches them by keyword, filtering by installed, not installed, updatable, or broken state. Use it to find app IDs before fetching details or installing.

Instructions

List the apps of the NAS app center, or search them by keyword. The output is a compact summary per app (app_id, name, install_status, installed_version, available_version); for full details and install parameters call nas_app_get. filter narrows the list to installed, not installed, updatable or broken apps. keyword (at most 20 characters) searches by name; a search can be combined only with filter "installed", and it does not find port apps or portal apps, so if nothing matches, list without keyword and look through the names. Always take app IDs from this output and confirm the choice with the user.

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

Input Schema

NameRequiredDescriptionDefault
filterNoOnly apps in this state.
keywordNoSearch term (max 20 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description goes further by describing the return shape (compact summary per app with app_id, name, install_status, versions) and flagging a real coverage limitation (searches miss port apps and portal apps). These are behavioral facts not derivable from the annotations or schema.

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?

Purpose is front-loaded, then output shape, then parameter caveats, then the ID-handling rule — a sensible order with no filler sentences. It is dense and runs several clauses long, so a slight structure penalty is fair, but every sentence carries operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating the returned fields, so an agent knows what it will receive. For a two-optional-parameter read tool with full schema coverage and annotations, nothing material is missing.

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%, so the baseline is 3, but the description adds genuine meaning: it translates the enum into human terms ('installed, not installed, updatable or broken') and states the inter-parameter constraint that a keyword search can only be combined with filter 'installed'. That constraint is invisible in the schema and prevents wasted calls.

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?

The description opens with a specific verb and resource ('List the apps of the NAS app center, or search them by keyword') and explicitly names the sibling that does the deeper job ('for full details and install parameters call nas_app_get'). An agent can distinguish list-vs-get without inspecting either schema.

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

Usage Guidelines5/5

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

It states exactly when to escalate to nas_app_get, what each filter state means, that keyword may only be combined with filter 'installed', and a concrete fallback ('if nothing matches, list without keyword and look through the names'). It even closes the loop on workflow ('confirm the choice with the user'), leaving little to inference.

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