The Longbridge MCP server exposes only a single tool (authenticate) with OAuth 2.1 functionality. The tool definition cannot be verified in the provided source code excerpt. The main.rs and Cargo.toml show HTTP transport via rmcp with Streamable HTTP support, but the actual tool schema, parameter definitions, and descriptions are not visible in the source provided. This is a critical gap: tool definitions must be directly inspectable in the codebase. Additionally, the tool marked as READ_ONLY (authenticate) suggests it is a read-only operation, but the MCP spec uses destructiveHint/idempotentHint/readOnlyHint annotations which are not evident. The server is production-grade infrastructure-wise (Rust, tokio, TLS support, prometheus metrics, structured logging) but tool quality cannot be assessed without visible schema definitions.

• Provide the full tool definition source (tools/mod.rs likely contains it). Include the explicit schema registration with JSON Schema types, descriptions, and constraints for every parameter.
• Expand tool description to 100-200 characters explaining: (1) What authenticate does (initiates OAuth 2.1 flow). (2) When to call it (before any credential-required tool). (3) What it returns (session token? bearer token? redirect URL?). (4) How long the session lasts.
• Document all parameters with type, description, and constraints. If authenticate accepts client_id, client_secret, scope, or redirect_uri, each must have a description and format constraint (e.g., 'client_id must be a 32-character alphanumeric string').
• Add readOnlyHint: false or destructiveHint: true if authenticate modifies server state (creates a session, logs events). Add idempotentHint: true if calling it twice with same input produces the same result without duplicates.
• Include error handling guidance in the description or via error examples: 'If authentication fails, returns one of: invalid_credentials, expired_token, unsupported_grant_type. Suggest user re-authenticate or check API key.'
• Expand the tool suite. Authentication alone is insufficient. Add tools to leverage the Longbridge API: search_stocks, get_quote, place_order, get_portfolio, etc. This enables real agent workflows.
• Add tool annotations to all future tools using the current MCP spec: readOnlyHint, destructiveHint, idempotentHint as booleans in the tool schema.

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

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry