Skip to main content
Glama
jmpijll

site24x7-code-mode-mcp

by jmpijll

Execute Site24x7 API calls

site24x7_execute

Execute custom JavaScript to call Site24x7 API, manage monitors, accounts, and tenancy across customers.

Instructions

Run Site24x7 API calls by writing JavaScript that uses the site24x7 namespace.

Surface:

  • site24x7.<tag>.<operationId>(args) — typed call. Args are auto-routed: keys matching path or query params from the spec are placed correctly; remaining keys form the JSON body for POST/PUT/PATCH. Override with { pathParams: {...}, query: {...}, body: {...}, version: '2.1', zaaid: '...' }.

  • site24x7.callOperation(operationId, args) — flat lookup by id.

  • site24x7.request({ method, path, query?, body?, version?, zaaid? }) — raw HTTP escape hatch (e.g. for endpoints not yet in the spec).

  • site24x7.spec{ title, sourceUrl, generatedAt, operationCount } for diagnostics.

  • site24x7.listCustomers() — MSP/BU customer enumeration (uses /api/short/msp/customers or /api/short/bu/business_units based on accountType).

  • site24x7.withCustomer(zaaid, async fn) — run fn(site24x7) with the closure scoped to a customer. Restores the previous zaaid on exit, even on throw. Must be awaited.

  • site24x7.zaaid — the currently active zaaid (or undefined).

Operations are async — use await. Top-level await is not supported; wrap in an async IIFE:

(async () => {
  const status = await site24x7.request({ method: 'GET', path: '/api/current_status' });
  return status;
})()

MSP recipe (fan out over customers)

(async () => {
  const customers = await site24x7.listCustomers();
  const out = [];
  for (const c of customers) {
    const status = await site24x7.withCustomer(c.zaaid, async (s) => {
      return s.request({ method: 'GET', path: '/api/current_status' });
    });
    out.push({ name: c.name, zaaid: c.zaaid, down: status?.monitors_status?.down ?? 0 });
  }
  return out;
})()

Errors

Errors are prefixed with a structured tag:

  • [site24x7.HttpError] HTTP 403 GET /api/users (operation requires scope(s) \Site24x7.Admin.Read` — confirm your refresh token grants them)`

  • [site24x7.MissingZaaidError] operation "..." requires a zaaid in scope (operation mspOnly=true). Hint: call site24x7.listCustomers() and wrap the call in site24x7.withCustomer(zaaid, ...).

  • [site24x7.MissingCredentialsError] ... when no Zoho OAuth credentials are configured

  • [site24x7.UnknownOperationError] ... when the operationId doesn't exist in the spec

Limits

  • Per-execute API call ceiling (default 50, configurable via SITE24X7_MAX_CALLS_PER_EXECUTE).

  • Sandbox memory + 30 s deadline.

  • Credentials never enter the sandbox.

  • Site24x7 enforces its own per-token rate limit (~10 req/s on most plans). 429 triggers one polite retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesJavaScript code to execute against the live Site24x7 API. Wrap async work in an IIFE.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses async nature, top-level await restrictions, error prefixes, limits (max calls, timeout), credentials handling, and retry on 429. This is thorough behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured with sections for surface, recipe, errors, limits. It is front-loaded with the main purpose and each paragraph adds value. Could be slightly more concise but efficient for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and one parameter, the description covers usage, errors, limits, and MSP pattern comprehensively. It lacks explicit return value format but demonstrates it in examples, making it nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with only one parameter `code` described minimally. The description adds significant meaning: code format (IIFE), namespace usage, error handling patterns, and MSP recipe, far exceeding the schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Run Site24x7 API calls by writing JavaScript that uses the `site24x7` namespace.' This is a specific verb (execute) and resource (Site24x7 API), and it distinguishes from the sibling tool `site24x7_search` by being a general execution tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides extensive usage patterns: typed calls, operationId, raw HTTP, MSP recipe, and error handling. It implicitly differentiates from `site24x7_search`, but lacks explicit 'when not to use' guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jmpijll/site24x7-code-mode-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server