Skip to main content
Glama

Server Details

Status keeps a team’s approved incident states and the exact customer-facing wording, then lets an assistant read that set before it posts an update. A 14-day trial, then Pro. The price is only at checkout.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 13 tools

Disambiguation4/5

The two evaluate_* tools are the closest pair, but the descriptions clearly separate audience-level permission (evaluate_audience) from exact-wording approval (evaluate_customer_update). The list_approved_causes / list_approved_statements / list_statement_limits trio and the corresponding save_* tools each target a distinct artifact type. get_status_context vs search_incident_states overlap somewhat (both surface incident states), but one is context retrieval and the other is paged search.

Naming Consistency5/5

All 13 tools use a clean snake_case verb_noun pattern: create_status_board, list_status_boards, get_status_context, save_approved_cause, evaluate_customer_update, search_incident_states, etc. The verb prefixes (create/list/get/save/evaluate/search) map predictably onto action types. No camelCase or mixed-convention deviations.

Tool Count4/5

13 tools sit comfortably in the well-scoped band and match the domain's distinct entity types (boards, causes, statements, limits, incident states) plus evaluation and read paths. There is mild redundancy—get_status_context already returns approved causes/timelines/workarounds that the three list_* tools expose separately—but nothing feels padded.

Completeness4/5

The core governance lifecycle is covered: create/list boards, save and read approved causes, statements, limits, and incident states, plus audience and wording evaluation. Gaps are revocation-oriented—there is no delete/update for boards and no way to retract or expire a previously approved cause/statement/limit, which matters for a governance surface. Agents can work around this by writing a superseding approval, so it is a minor rather than blocking gap.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources