The OKR Manager MCP server has 6 tools covering objective and key result management. All tools have descriptions and input schemas visible in the source code (api/OKRManagerMCP.ts). However, there are significant gaps in parameter descriptions, missing output schema documentation, and no error handling guidance. Tool names follow verb_noun convention reasonably well (listObjectives, addObjective, deleteObjective, addKeyResult, setKeyResultAttainment, deleteKeyResult), but parameter descriptions are minimal or missing entirely. The server lacks documentation of return types, pagination support, and error recovery patterns. Most tools are READ_ONLY or WRITE/DESTRUCTIVE, but there is no confirmation mechanism for destructive operations. Output formatting is hardcoded in formatResponse() but not formally documented as part of the tool contract.

• Add explicit output schema documentation for all tools. Document the Objective[] structure returned: {id: string, text: string, keyResults: {id: string, text: string, attainment: number}[], ...}. Include field types, required fields, and example values.
• Expand parameter descriptions with format guidance. E.g., okrID: 'UUID of the objective (e.g., 550e8400-e29b-41d4-a716-446655440000)'. keyResultText: 'Text describing the key result (max 500 characters, required)'. attainment: 'Progress as a percentage from 0 (not started) to 100 (complete)'.
• Add error handling documentation. Document: 'Returns error if okrID does not exist. Returns error if user lacks delete:objectives permission. If permission denied, try requesting elevated access from an administrator.'
• Implement confirmation step for destructive operations. Add optional 'confirm_delete: boolean' parameter to deleteObjective and deleteKeyResult, or create separate tools: delete_objective_confirm(okrID) that returns {confirmation_id, message} and delete_objective_execute(confirmation_id) that performs the deletion.
• Add pagination to listObjectives. Accept limit (default 50, max 500) and offset parameters. Return {objectives: [...], total: number, has_more: boolean}. Document the limit in the description.
• Declare required permissions in each tool description. E.g., addObjective: 'Requires create:objectives permission. Verify your role has write access to organization settings.'
• Add validation error messages. When attainment is outside 0-100, return: 'Invalid attainment: 150. Must be between 0 and 100.' When okrID not found, return: 'Objective not found. Call listObjectives to see available objectives.'

Inferred effective spec: <=2025-11-25.

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