← Leaderboard
7.2 L3

Slack

Ready Assessed · Docs reviewed · Mar 11, 2026 Confidence 0.82 Last evaluated Mar 11, 2026

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

7.8
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

6.4
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

7.2

Autonomy breakdown

P1 Payment Autonomy
6.0

Slack app distribution via marketplace; billing API limited

G1 Governance Readiness
8.0

Enterprise Grid has strong RBAC and audit; free/pro tiers limited

W1 Web Agent Accessibility
6.0

Complex web UI; bot/app APIs are well-structured for agents

Overall Autonomy 6.7/10
Ready for agent use

Active failure modes

  • HIGH

    Bot token vs user token confusion

    Some Slack API methods require user tokens (xoxp-), others accept bot tokens (xoxb-). Documentation doesn't always clearly distinguish. Agents using wrong token type get cryptic "not_authed" errors.

    Agent impact: Agent fails on specific operations (e.g., searching messages) because it uses bot token where user token is required. Error message doesn't indicate token type mismatch.

    Workaround: Maintain both token types. Check method documentation for required token type. Map operations to token types at initialization.

    common auth
  • MEDIUM

    Per-method rate limits with no global header

    Slack rate limits are per-method, not global. There's no single header showing remaining quota across all methods. Agents must track limits per-endpoint.

    Agent impact: Agent hits rate limit on chat.postMessage while other methods are fine. Global rate limiting strategies don't work — must be per-method.

    Workaround: Implement per-method rate tracking. Use Slack's Retry-After header. Prioritize critical messages (alerts) over bulk operations (channel history).

    common rate-limiting

Use in your agent

mcp
get_score ("slack")
● Slack 7.2 L3 Ready
exec: 7.8 · access: 6.4

Trust & provenance

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L3 Ready

7.2 / 10.0

Alternatives

No alternatives captured yet.