Scribase

environment.create

Provision an environment. POST /v1/environments. kind is preview, staging, or production; data_mode is schema_only, sanitized, or snapshot.

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": {
      "organization_id": "<organization_id>",
      "project_id": "<project_id>",
      "environment_id": "<environment_id>",
      "kind": "<kind>",
      "data_mode": "<data_mode>",
      "region": "<region>",
      "idempotency_key": "<idempotency_key>",
      "confirm": "<confirm>"
    },
    "name": "environment.create"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	kind (required)
`region`	Yes	region (required)
`confirm`	Yes	Must be true to apply this mutation; otherwise the tool returns the request it would send for approval.
`data_mode`	Yes	data_mode (required)
`ttl_hours`	No	Auto-expiry in hours
`project_id`	Yes	project_id (required)
`environment_id`	Yes	environment_id (required)
`postgres_major`	No	Postgres major version (default 17)
`idempotency_key`	Yes	idempotency_key (required)
`organization_id`	Yes	organization_id (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the bar is lower. The description adds that this is an HTTP POST to /v1/environments, but says nothing about cost, provisioning time, side effects, or how the confirm-gated approval flow behaves, all of which matter for a create-infrastructure call.

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?

Three short sentences, front-loaded with the action, with no filler or repetition. The bare endpoint token is borderline but does carry information the agent can use; the telegraphic enumeration style is efficient though slightly clipped.

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

Completeness3/5

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

For a 10-parameter, 8-required infrastructure-mutation tool with no output schema, the definition covers the action and the two closed value sets but omits the confirm-gated dry-run behavior, idempotency expectations, and any notion of what a successful provision returns. The confirm parameter's schema description partially backfills the approval flow, but the description itself leaves material gaps.

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 coverage is nominally 100%, but most property descriptions are bare placeholders like "kind (required)" and "region (required)", so the description's enumeration of kind (preview/staging/production) and data_mode (schema_only/sanitized/snapshot) is genuinely additive value not present in structured fields. It adds nothing, however, about idempotency_key semantics or the org/project/environment identifier relationships across the 8 required params.

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?

States a specific verb and resource ("Provision an environment") plus the underlying endpoint, which unambiguously separates it from environment.list, environment.get, environment.delete, and environment.suspend. An agent can identify the create-environment tool without opening a schema.

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?

No guidance on when to call this versus alternatives such as projects.create, projects.list, or environment.list, and no stated prerequisites (existing org/project, permissions). Usage is only implied by the verb "Provision".

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?