spikesh
Server Details
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
16 toolsspike_acknowledge_incidentsAcknowledge incidentsDestructiveInspect
ACKNOWLEDGES one or more incidents — this CHANGES live incident state (stops escalation and marks them as being worked on). Spike: POST /incidents/acknowledge with {ids:[...]}.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | Incident ids (the incident `_id` values) to acknowledge. | |
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
spike_get_escalationGet escalation policyRead-onlyInspect
Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. | |
| escalationId | Yes | The escalation policy's _id (from spike_list_escalations). |
spike_get_incidentGet incidentRead-onlyInspect
Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. | |
| counterId | Yes | The incident's counterId (its human-facing incident number/id). |
spike_get_incident_activity_logGet incident activity logRead-onlyInspect
Get the chronological activity log for an incident — {incident, activities:[...]} (who acknowledged/resolved/commented and when). Spike: GET /incidents/{counterId}/activity-log (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. | |
| counterId | Yes | The incident's counterId. |
spike_get_on_callGet on-call scheduleRead-onlyInspect
Get one on-call schedule by id — {oncall:{_id, name, timezone, teams, users, activeShift, renderedShifts}}. from optionally sets the window start for rendered shifts. Spike: GET /on-calls/{oncallId} (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| from | No | ISO timestamp to render upcoming shifts from (e.g. "2026-07-19T00:00:00Z"). | |
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. | |
| oncallId | Yes | The on-call schedule's id (from spike_list_on_calls). |
spike_get_serviceGet serviceRead-onlyInspect
Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. | |
| counterId | Yes | The service's counterId (from spike_list_services). |
spike_list_acknowledged_incidentsList acknowledged incidentsRead-onlyInspect
List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
spike_list_escalationsList escalation policiesRead-onlyInspect
List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
spike_list_incidentsList incidentsRead-onlyInspect
List incidents for a team — {incidents:[...], totalIncidents, totalOpenIncidents, pagination}. Each incident carries title, status, priority, severity, and timing. Spike: GET /incidents (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number for pagination. | |
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. | |
| perPage | No | Results per page. |
spike_list_on_callsList on-call schedulesRead-onlyInspect
List a team's on-call schedules — {oncalls:[...]}. Each on-call has an id, name, timezone, and layers. Use the id with spike_get_on_call / spike_who_is_on_call_next. Spike: GET /on-calls (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
spike_list_servicesList servicesRead-onlyInspect
List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
spike_list_teamsList teamsRead-onlyInspect
List all teams in the Spike.sh organization — {teams:[{_id, name, uid, private, org}]}. NOT team-scoped (no x-team-id needed). The _id values here are what you pass as teamId (x-team-id) to every other tool. Spike: GET /teams/get-all-teams.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
spike_list_triggered_incidentsList triggered incidentsRead-onlyInspect
List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
spike_resolve_incidentsResolve incidentsDestructiveInspect
RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | Incident ids (the incident `_id` values) to resolve. | |
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
spike_set_incident_prioritySet incident priorityADestructiveInspect
Sets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | Incident ids (the incident `_id` values) to update. | |
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. | |
| priority | Yes | Priority level: p1 (highest) .. p5 (lowest). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already include destructiveHint true. The description adds that it 'CHANGES live incident state,' which reinforces but does not significantly extend beyond annotations. No mention of permissions, rollback, or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with the main action front-loaded. The second sentence includes the API endpoint, which may be extraneous for an AI agent but does not harm conciseness. No superfluous content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema, and the description lacks information about return values or confirmation of the update. Given the mutation nature, additional context on what happens after successful operation would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% as all parameters have descriptions in the schema. The description provides an example request format but does not add new meaning beyond what the schema already conveys.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Sets') and the resource ('incidents') with a specific attribute ('PRIORITY (p1..p5)'), and it distinguishes from sibling tools that handle other incident actions like acknowledging or resolving.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly state when to use this tool versus alternatives. It mentions that it changes live incident state, which implies it's for mutation, but no guidance on prerequisites or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
spike_who_is_on_call_nextWho is on call nextRead-onlyInspect
Get the NEXT scheduled shift for an on-call schedule — {nextShift:{userId, startTimeInUTC, endTimeInUTC}} (or {} if none). Spike: GET /on-calls/{oncallId}/who-is-on-call-next (team-scoped).
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. | |
| oncallId | Yes | The on-call schedule's id. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!