Scribase

environment.resume

Resume a suspended environment. POST .../environments/{env}/resume.

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>",
      "idempotency_key": "<idempotency_key>",
      "confirm": "<confirm>"
    },
    "name": "environment.resume"
  }
}

Input Schema

Name	Required	Description
`confirm`	Yes	Must be true to apply this mutation; otherwise the tool returns the request it would send for approval.
`project_id`	Yes	project_id (required)
`environment_id`	Yes	environment_id (required)
`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.2/5.0

Behavior2/5

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

Annotations already declare the mutation safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false). The description adds only the HTTP path, saying nothing about what state transition occurs, whether resumption can fail or is reversible, or that in-flight work resumes. Notably, idempotentHint=false sits oddly with a required idempotency_key, and the description does nothing to clarify that tension.

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?

Two short clauses, front-loaded with the action and followed by the endpoint mapping; nothing is padded. The endpoint string is marginally redundant with the tool name but is a reasonable orientation cue.

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 five-required-parameter mutation with no output schema, the description plus schema covers the mechanics adequately, and annotations handle the safety profile. However, an agent gets no description-level warning about the approval-gated behavior or failure modes, which are exactly the details that matter most for a write operation.

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 the key semantic detail – that confirm must be true or the tool returns a dry-run request for approval – is documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline 3 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 opens with a specific verb+resource pair ("Resume a suspended environment") that is unmistakable and implicitly distinct from the sibling environment.suspend and environment.delete. It stops short of naming a sibling or stating scope boundaries, so a 5 is not warranted.

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 the state condition "suspended" – an agent can infer this only applies to an environment already suspended. There is no explicit when-not guidance, no mention of the confirm/approval gate at the description level, and no routing to alternatives such as environment.suspend.

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?