Skip to main content
Glama
jmpijll

site24x7-code-mode-mcp

by jmpijll
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Search Site24x7 API spec

site24x7_search

Search the Site24x7 REST API spec via JavaScript to find operations by query, path, tag, or operation ID. Use it to discover endpoints before execution.

Instructions

Search the Site24x7 REST API spec by writing JavaScript.

The sandbox is read-only — no network. Use this tool to discover what to call before invoking site24x7_execute.

Globals

  • spec — { title, sourceUrl, generatedAt, operationCount, tags[] }. null if no spec is loaded.

  • searchOperations(query, limit?) — text-ranked search; default limit 25.

  • getOperation(operationId) — full operation including parameters, requiredScopes, mspOnly / buOnly flags. Returns null if no such id.

  • findOperationsByPath(substring) — list operations whose path contains the substring (case-insensitive).

  • findOperationsByTag(tag) — list operations in a tag (e.g. 'monitors', 'msp', 'business_units').

  • console.log() — captured into the tool output.

Examples

// All operations tagged "monitors"
findOperationsByTag('monitors');
// Top 10 hits for "msp customer"
searchOperations('msp customer', 10);
// Full detail on the create-monitor op
getOperation('post_monitors');

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesJavaScript code to execute against the bundled spec. The final expression is returned.

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

No annotations are provided, but the description fully discloses behavioral traits: 'The sandbox is read-only — no network.' It also lists available globals and their behaviors (searchOperations, getOperation, etc.), providing comprehensive transparency.

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

Conciseness5/5

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

The description is well-structured with headings, bullet points, and code blocks. It front-loads the purpose and usage guidance, and every sentence adds value without redundancy.

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?

The description adequately covers the tool's context given the lack of output schema. It explains how `console.log` is captured and that the final expression is returned. However, it could explicitly mention error handling or return format for edge cases.

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

Parameters4/5

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

The input schema covers 100% of parameters (single `code` parameter). The description adds value by explaining that the final expression is returned and provides examples of usage patterns, though the schema already describes the parameter well.

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 the verb 'search' and resource 'Site24x7 REST API spec'. It explicitly distinguishes from the sibling tool `site24x7_execute` by noting 'Use this tool to discover what to call before invoking site24x7_execute'.

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

Usage Guidelines5/5

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

The description explicitly says when to use this tool ('discover what to call') versus the sibling tool ('before invoking site24x7_execute'). It also implies not to use for execution since the sandbox is read-only.

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