Scribase

OTA update status

ota.status

Read-onlyIdempotent

Whether over-the-air updates are set up on this branch, the update URL the app reads, and the newest release per platform and channel. Set it up with capabilities.add slot ota (or scribase ota setup); publish with the unmodified hot-updater CLI (npx hot-updater deploy -p ios). Scope: functions: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": "ota.status"
  }
}

Input Schema

Name	Required	Description
`branch`	No	Branch (environment) id. Optional: defaults to `production`.
`project_id`	No	Project id. Optional: defaults to the project created or used last in this session, or the only one.
`organization_id`	No	Organization id. Optional: defaults to the token's organization, or the only one you belong to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description contributes genuinely new behavioral context: the required scope `functions:read` and the fact that setup/publish happen through other surfaces (capabilities.add or the unmodified hot-updater CLI), which signals this tool is read-only by design and cannot configure anything itself.

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 first sentence is front-loaded and carries the actual return semantics; the second adds operational next steps. The publish command (`npx hot-updater deploy -p ios`) is somewhat tangential for a status read and borders on noise, but the overall size is small and nothing is buried.

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?

With no output schema, the description carries the burden of describing returns, and it does so concretely (setup flag, update URL, newest release per platform and channel), plus the auth scope. It stops short of saying what the response looks like when OTA is not set up on the branch, which is the one obvious gap for a status tool.

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% and all three parameters are optional with their defaults (`production`, session project, token organization) documented in the schema. The description adds no branch/project/org resolution detail beyond that, so the baseline 3 for a fully documented schema applies.

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 names the resource (OTA update status on a branch) and enumerates the concrete outputs: whether OTA is set up, the update URL the app reads, and the newest release per platform and channel. That is far more specific than a restatement of the title, but it never contrasts itself with the sibling read tools ota.releases or ota.rollback, so an agent must infer which OTA tool to reach for.

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

Usage Guidelines3/5

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

Usage is only implied: the mentions of capabilities.add slot ota and the `npx hot-updater deploy` publish flow suggest this tool answers 'is OTA configured and what's live', which makes the check-before-publish workflow inferable. There is no explicit statement of when to call this instead of ota.releases, nor of when it is unnecessary, so the guidance is context-adjacent rather than directive.

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

All Scribase tools Inspect

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

Need Help?