nc-mcp-server

get_app_info

Read-onlyIdempotent

Retrieve metadata for an installed Nextcloud app, including name, version, description, and author. Requires admin privileges.

Instructions

Get detailed information about an installed Nextcloud app. Requires admin privileges.

Returns app metadata including name, version, description, and author.

Args: app_id: The app identifier (e.g. "spreed", "mail", "collectives"). Use list_apps to find available app IDs.

Returns: JSON object with app details: id, name, summary, version, author.

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": {
      "app_id": "<app_id>"
    },
    "name": "get_app_info"
  }
}

Input Schema

Name	Required	Description	Default
`app_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark the operation read-only, idempotent, and non-destructive. The description adds the admin-privilege requirement and specifies the returned metadata fields. No contradiction with annotations.

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?

The description is front-loaded and well structured with Args/Returns sections. However, the return information is stated twice with slightly different field lists, adding minor redundancy.

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 low-complexity, single-parameter read tool with annotations and an output schema, the description covers permissions, parameter resolution, and return shape. Error behavior for missing or unauthorized apps is not described, but this is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema gives app_id no description (0% coverage), but the description compensates by identifying it as an app identifier, providing concrete examples ('spreed', 'mail', 'collectives'), and directing to list_apps for ID resolution. This fully covers the single parameter.

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 ('Get detailed information about an installed Nextcloud app'), names the output domain (app metadata), and notes admin privileges. It also points to list_apps for finding app IDs, which helps distinguish this single-app lookup from sibling app-management tools.

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?

Explicitly states the prerequisite (admin privileges) and directs the agent to use list_apps to discover valid app_id values. It does not enumerate exclusions or alternatives, but the context for when to call this tool is clear.

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

Deploy Server