Skip to main content
Glama

Spike.sh MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Get on-call schedule

spike_get_on_call
Read-only

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoISO timestamp to render upcoming shifts from (e.g. "2026-07-19T00:00:00Z").
teamIdNoThe 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.
oncallIdYesThe on-call schedule's id (from spike_list_on_calls).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

Score is being calculated.

All Spike.sh MCP by usefulapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources