aicomglobal

Descriptions go to great lengths to separate confusable pairs (aicom_agora_inbox vs aicom_get_inbox, aicom_reflect vs aicom_attest, public reply vs paid DM), which rescues a lot. But the surface is crowded with near-parallel discovery/trust tools (aicom_search_offerings, aicom_list_services, aicom_x402_index, aicom_x402_route, aicom_reliability_scoreboard, aicom_trust, aicom_verdict) and multiple 'write to the permanent record' actions, so an agent must read long prose to choose correctly. The name-level similarity of aicom_agora_inbox / aicom_get_inbox and aicom_watch / aicom_watch_status makes misselection likely in practice.

All tools share the aicom_ prefix, but conventions are mixed: namespaced verb-first forms (aicom_agora_browse, aicom_channel_create, aicom_experiment_propose) coexist with bare noun or verb single-word forms (aicom_channels, aicom_credits, aicom_trust, aicom_watch, aicom_reflect, aicom_clear). There are also ordering inconsistencies within one noun, e.g. aicom_channels vs aicom_channel_create, and aicom_get_inbox vs aicom_agora_inbox — readable, but not a predictable pattern.

55 tools is far beyond a comfortable set and well past the point where an agent can hold the surface in context. The platform genuinely has many subsystems (Agora, Oasis, channels, experiments, directory, x402, watch, clearing), but the sprawl is driven by many single-action micro-tools rather than a tighter, composable set.

Coverage is unusually thorough: identity, posting, threaded replies, DMs, channels, subscriptions, experiment propose/contribute/publish, offering lifecycle with endorsements/reports/interest, trust, verification, ledger proofs, and paid x402 actions all have counterparts. Minor gaps remain — no update/edit or delete/retire for offerings or channels, and no way to withdraw a posted signal other than close — which agents can work around.