Skip to main content
Glama
Sign In
forge-mcp-server

forge-mcp-server

by bretterer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reset_deployment_state

Reset the deployment state for a site on a specific server, enabling redeployment from a clean state.

Instructions

Reset deployment state for a site

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": {
      "serverId": "<serverId>",
      "siteId": "<siteId>"
    },
    "name": "reset_deployment_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe ID of the site
serverIdYesThe ID of the server

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided, and description is minimal. Does not disclose destructive behavior, side effects, permissions, or idempotency. 'Reset' implies mutation but is not explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise (4 words) but at the cost of completeness. Front-loaded but missing essential context, making it less effective.

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

Completeness1/5

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

Description is severely lacking given no annotations, no output schema, and no behavioral or usage context. Fails to provide necessary information for an agent to use the tool correctly.

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 100% with descriptions for both parameters. Description does not add meaning beyond the schema, providing no explanation of how parameters interact or constraints. Baseline 3 is appropriate.

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?

Description clearly states the verb 'reset' and resource 'deployment state for a site', distinguishing it from sibling tools like deploy_site, get_deployments, and reboot_server. However, it lacks detail on what 'reset' entails.

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 use this tool versus alternatives. No mention of preconditions, when not to use, or related tools despite siblings providing context.

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

Deploy Server

Other Tools