Bunstation

Get Cloud

projects_cloud_get

Read-onlyIdempotent

Read Bunstation Cloud for a project: Postgres, Auth, HTTP endpoints, and cron jobs. database.url, auth.service_role_key, and auth.jwt_secret are secrets. Do not write them into public website source. Login and signup use projectUrl/auth/v1 with the anon key. Custom HTTP uses publicHost.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "projects_cloud_get"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes	UUID of a Bunstation project owned by the authenticated user.

Output Schema

Name	Required	Description	Default
`auth`	Yes
`name`	Yes
`crons`	Yes
`quota`	Yes
`status`	Yes
`database`	Yes
`connected`	Yes
`endpoints`	Yes
`projectRef`	Yes
`projectUrl`	Yes
`publicHost`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive operation. The description adds valuable context beyond that by identifying secret fields and warning not to write them into public website source, plus noting how login/signup and custom HTTP values should be used.

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 front-loaded with the purpose, then immediately covers secret handling and endpoint usage in short, efficient sentences. Every sentence adds practical value for an agent using the returned cloud data.

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?

For a simple one-parameter read tool with a full output schema and safety annotations, the description is largely complete: it explains what is read, which returned values are secret, and how to use key endpoints. The main remaining gap is explicit sibling routing, which would help an agent choose this over narrower cloud subresource tools.

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?

There is only one parameter, project_id, and the schema already fully describes it as a UUID of a Bunstation project owned by the authenticated user. The description adds no parameter-level meaning beyond the schema, which is acceptable given 100% schema coverage.

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 states a specific read operation ('Read Bunstation Cloud for a project') and scopes it to Postgres, Auth, HTTP endpoints, and cron jobs. It lets an agent tell this apart from mutation siblings like projects_cloud_enable or projects_cloud_stop, but it does not explicitly differentiate this aggregate read from narrower siblings such as projects_cloud_cron_get.

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 implied by 'Read Bunstation Cloud for a project,' which suggests retrieving cloud configuration. However, the description gives no explicit when-to-use guidance and no alternatives for accessing narrower cloud resources, so the agent must infer the boundary from sibling names.

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

All Bunstation tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?