Staticbot MCP server

get_account_status

Read-only

Check account status to identify connected integrations, plan entitlements, and the pending action that must be completed before starting a deployment or migration.

Instructions

START HERE. The first call of any Staticbot conversation, and the cheapest: it answers in one request who the credential belongs to, which integrations are connected, what the plan allows, and what is actually outstanding — so you never propose work whose prerequisites are missing. Read pendingAction and follow it, exactly as you would follow a migration's pendingAction: • CONNECT_SOURCE_CONTROL / CONNECT_DATABASE — nothing can start. Give the user the url and stop; do not propose a migration or a deployment until they have connected it and you have called this tool again. • CHOOSE_PATH — everything required is connected. Staticbot does two different things and the user's goal decides which: start_hosting (deploy the repository, keep building where they build today, nothing about the app's backend changes) and start_migration (move the app's database, auth, storage and functions onto infrastructure they own, leaving the builder's backend behind). ASK which one they want. Do not infer it from the fact that they asked about repositories, and do not default to migration. Each entry in nextActions carries available, blockedBy, blockedReason and the tool that begins it. A blocked entry is still listed on purpose — it is how you tell 'needs one more connection' apart from 'Staticbot cannot do this', and blockedReason is written to be shown to the user verbatim. Contains no secrets.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Parsed JSON response from the Staticbot public API

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.8.1Sep 24, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial behavioral context: it explains that pendingAction must be followed exactly, describes the structure and purpose of nextActions, and notes that blocked entries are intentionally listed. It also assures the agent that the response contains no secrets, providing extra safety information beyond the annotations.

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 long but every sentence carries weight. It front-loads the critical instruction ('START HERE') and purpose, then uses clear bullet points to explain pendingAction branches and nextActions semantics. The structure is highly organized, with no filler, making it easy for an agent to parse and act on.

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

Completeness5/5

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

Given that the tool has an output schema that documents return values, the description covers all necessary contextual aspects: when to call, how to interpret the response, how to handle pendingAction, and how to use nextActions. It even addresses edge cases like blocked entries and warns against premature actions, making it complete for its role as a conversational starting point.

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 tool has zero parameters, so there is nothing for the description to explain about parameters. The baseline for 0 parameters is 4, and the description correctly focuses on output behavior rather than parameter usage, which is appropriate here.

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 tool's purpose: it is the first call in any Staticbot conversation, providing identity, integrations, plan limits, and outstanding actions in one request. It explicitly differentiates itself from siblings by being the starting point and the cheapest option, making it unmistakable which tool to use first.

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 provides explicit when-to-use guidance ('START HERE', 'The first call of any Staticbot conversation') and detailed instructions on how to react to each pendingAction value, including when to stop and ask the user versus when to proceed. It also warns against inferring choices and gives clear direction on following nextActions, making the usage context fully explicit.

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

Deploy Server