Server has only 2 tools, both authentication-focused. Tool naming follows verb_noun pattern (nc_auth_provision_access, nc_auth_check_status), which is good. However, descriptions are minimal (under 150 chars each), and critically, NO input schemas are visible in the provided source code. The first tool accepts a 'scopes' parameter (array of strings) but the schema definition is not shown. The second tool has empty input ({}). Without visible schema definitions, parameter types, and constraints, LLMs cannot validate inputs or understand what values are acceptable. Descriptions exist but lack actionable detail about prerequisites, return values, or error conditions. No output schemas documented. Risk annotations present (WRITE, READ_ONLY) but insufficient for production use.

• Add complete JSON Schema definitions for both tools. For nc_auth_provision_access, define the 'scopes' parameter with type array, items type string, and an enum of valid scope values (e.g., ['notes:read', 'calendar:write', 'files:read', ...]). For nc_auth_check_status, explicitly define empty input as type object with no required properties.
• Document output schemas for both tools. Specify what ProvisionAccessResponse and ProvisionStatusResponse contain (e.g., login_url, device_code, status, expires_in, user_id). Include field types and whether fields are nullable.
• Expand descriptions to 100-200 characters with actionable detail. Example for Tool 1: 'Initiate Nextcloud Login Flow v2 to obtain an app password. Returns a login URL and device code. User must open the URL in a browser and authorize the requested scopes. Call nc_auth_check_status to poll for completion.'
• Add error handling guidance to descriptions. Example: 'If scopes are invalid, returns error with list of valid scopes. If polling times out after 10 minutes, retry with a new device code.'
• Document the polling contract for Tool 2: what status values are possible (pending, authorized, expired), what the response contains at each stage, and when to stop polling.

Inferred effective spec: 2026-07-28+.

• Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)