Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

Uptime status

uptime.status
Read-onlyIdempotent

The project's uptime checks with their current state (up, down or waiting), last result and public status page. Scope: projects:read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uptime.status"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNoBranch (environment) id. Optional: defaults to `production`.
project_idNoProject id. Optional: defaults to the project used last in this session, or the only one.
organization_idNoOrganization id. Optional: defaults to the token's organization, or the only one you belong to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavior beyond annotations by naming the required scope (projects:read), listing the possible check states, and describing the returned data. It does not mention pagination or result ordering, but for this simple read-only tool the added context is solid.

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 a single tightly written sentence with no filler. The operational content is front-loaded and the scope requirement is appended clearly.

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?

This is a simple read-only status tool with three optional parameters, fully documented in the schema, and no output schema. The description gives enough context about what is returned and the required scope, though it could be slightly more complete by clarifying pagination or list behavior.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains all three optional parameters and their defaults. The description does not add any parameter-specific meaning beyond what the schema provides, which is the expected baseline here.

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

Purpose4/5

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

The description clearly identifies the resource (uptime checks) and what information is returned: current state, last result, and public status page. It does not explicitly contrast with sibling status tools such as addon.status, import.status, or push.status, but the resource-specific wording makes the tool distinguishable.

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

Usage Guidelines2/5

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

The description implies that the tool is for retrieving a project's uptime checks, but it gives no explicit when-to-use guidance, exclusions, or alternatives. It does not say when to choose this over project.get, metrics.get, or other status-oriented siblings.

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

All Scribase 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