Texas Grocery MCP has 27 tools with consistent naming (verb_noun pattern) and basic schemas. Most tools have descriptions (10-100 chars, below the 50-200 char ideal). Input schemas are present but sparse, many parameters lack descriptions or type constraints. Output schemas are not documented. Error handling is minimal; no recovery guidance visible. Security concerns: session_save_credentials exposes passwords as parameters (critical). Composition is reasonable (single responsibility per tool), but batch variants (cart_add_many, product_search_batch) exist alongside single-item tools, creating redundancy. No pagination documented for list operations.

• Move email and password from session_save_credentials parameters to environment variables or a secure vault. Implement server-side credential injection so agents never handle raw secrets.
• Document output schemas for all 27 tools. Specify field names, types, and which fields are required for chaining (e.g., product_get must return sku, price, availability for downstream cart_add calls).
• Add explicit pagination to list tools: include offset/limit or cursor parameters, return total_count, and cap results at 20-50 items. Document the limit in each tool description.
• Consolidate cart_add + cart_add_many into a single cart_add tool that accepts items as an array (with single-item convenience). Same for product_search variants. Reduce LLM decision overhead.
• Add error handling with recovery guidance: document which errors are retryable (network timeouts, rate limits) vs user-fixable (invalid SKU, auth required) vs fatal. Include actionable messages like 'SKU not found. Try product_search() first.'

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

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