mcp-rpc is a library/framework for building MCP servers with type-safe RPC patterns, evaluated via its example server. The 3 tools in examples/nextjs/src/app/[transport]/handler.ts show minimal but functional definitions. Tool names start with action verbs (echo, list, get), and all have descriptions present. However, parameter descriptions are sparse or missing, output schemas are not documented, and error handling is absent. The framework itself registers tools with McpServer.tool() passing descriptions and Zod input schemas, which is correct, but the example tools do not leverage full documentation potential. Parameter constraints are minimal, most are simple strings without format validation or range specifications. Output format is hardcoded to {content: [{type: 'text', text: string}]} with no schema documentation for consumers. The codebase shows good typing patterns (Zod integration, TypeScript generics) but weak documentation discipline for agent consumption.

• Add paginated-result pattern to organisations.list: accept limit (default 20, max 100) and offset/cursor parameters. Return {items: [...], total: number, hasMore: boolean}. Document in tool description: 'Returns paginated list of organisations. Default limit 20. Use offset to fetch additional pages.'
• Document output schema for all tools. Add to tool description or as a comment in code: 'Returns {content: [{type: "text", text: string}]}' so LLM knows structure for chaining.
• Expand organisations.list description to 50-150 chars: 'List all organisations in the database. Returns paginated results (max 100 per page). Use limit and offset to navigate. Useful for discovering available orgs before calling get.'
• Enhance organisations.get parameter 'id' description: 'Organisation ID (string, e.g. "550e8400-e29b-41d4-a716-446655440000"). If organisation not found, error will indicate valid IDs available from list.' Add error guidance in handler: catch NotFound, return 'Organisation not found. Call organisations.list to see available IDs.'
• Implement error handling in handlers. Wrap organisations.get logic: if org not found, return {content: [{type: 'text', text: `Organisation ${input.id} not found. Available IDs: ${availableIds.join(', ')}`}]} instead of silent failure.
• Consider flattening tool names from organisations.list → list_organisations, organisations.get → get_organisation for standard verb_noun naming and compatibility with broader MCP ecosystem expectations.