Particle

Agent readability score

Strengths

• Tool names clearly indicate their purpose (e.g., particle_alert_create, particle_podcast_search_transcripts).
• Descriptions provide actionable context for usage scenarios (e.g., 'soft delete' behavior in particle_alert_delete).

Weaknesses

• Some descriptions are overly technical without explaining *when* to use the tool (e.g., particle_call's 'compatibility fallback' explanation).
• Parameter schemas and constraints (e.g., required vs. optional fields) are not explicitly documented in descriptions.
• No explicit error handling or validation rules are mentioned for any tool.

• particle_call — Vague description lacks context for when/why to use the fallback tool
• particle_catalog — No clear use case explained for browsing the tool catalog
• particle_entity_resolve — Missing explicit parameter constraints (e.g., required fields)
• particle_podcast_find_mentions — No error handling details for invalid entity slugs

Verdict

The Particle MCP tools demonstrate strong intentionality in naming and functionality, but lack explicit parameter documentation and error handling guidance. This creates minor ambiguity for agents needing precise tool usage boundaries.

9/11/2026, 6:08:45 AM

Event narrative

Server transitioned to 'legacy' era with 100 compliance score after unknown state.

Risk: medium

• 2026-09-10T21:16:35.016Z — Era changed to 'unknown' · Server in unknown state with no compliance data
• 2026-09-11T05:44:28.819Z — Era set to 'legacy', compliance score 100 · Server stabilized in legacy mode with full compliance

Advice

Monitor server stability in legacy mode and verify compliance score remains at 100. Investigate the transition from 'unknown' to 'legacy' to ensure it was intentional.