Three tools with significant definition gaps. 'echo' and 'list_environments' have minimal descriptions (under 50 chars). 'dynamic_bruno_api_tools' has a generic description that doesn't explain when/why to use it. Parameter descriptions are present but sparse. No output schemas documented. No error handling guidance. Tool names lack clear action verbs for discovery tools. Schema definitions exist but lack constraints (enums, ranges, patterns).

• Expand 'echo' description to 100-150 chars: 'Echo back a message for testing. Use this to verify the MCP server is responding correctly. Returns the input message unchanged.'
• Expand 'list_environments' description: 'List all available environments defined in the Bruno API collection. Call this first to see which environments (dev, staging, prod) are available before executing requests. Returns environment names and their configuration.'
• Remove the dummy 'random_string' parameter from 'list_environments'. Make it a zero-parameter tool. If the schema requires at least one property, use an optional 'filter' parameter instead.
• Document output schemas for all tools. Add a 'returns' section to each tool description or create a separate schema definition. E.g., 'echo returns {message: string}', 'list_environments returns {environments: [{name: string, description?: string}]}'.
• Add enum constraints to 'environment' parameter in 'dynamic_bruno_api_tools'. Populate it dynamically from list_environments() or document valid values. Add min/max length to 'variables' and 'query' string values.

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

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