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

forge-mcp-server

by bretterer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

toggle_quick_deploy

Enable or disable quick deploy on a specific site and server. Provide server ID, site ID, and boolean flag to toggle.

Instructions

Enable or disable quick deploy 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>",
      "enable": "<enable>"
    },
    "name": "toggle_quick_deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
enableYesWhether to enable or disable quick deploy
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.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states the function without addressing side effects, permissions, or immediacy of changes. The agent has no information about what happens when this setting is toggled.

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?

The description is very brief and front-loaded, which is good for conciseness. However, it is too minimal; it lacks any supplementary context that would justify its brevity.

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

Completeness2/5

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

Given the three required parameters and no output schema, the description should elaborate on the nature of 'quick deploy' and the effects of toggling. Without this, the tool is not fully contextualized for an agent.

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%, so the schema already explains each parameter adequately. The description adds no extra meaning beyond the schema, meeting the baseline for high-coverage cases.

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 clearly states the action ('enable or disable') and the resource ('quick deploy for a site'), making the tool's purpose evident. However, it does not explicitly distinguish this toggle setting from sibling tools like 'deploy_site', which might confuse an agent.

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 is provided on when to use this tool versus alternatives, nor are there any prerequisites or context for enabling or disabling quick deploy. The agent must infer usage from the tool name and parameters.

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