Skip to main content
Glama
Sign In
Scout MCP Server

Scout MCP Server

Official
by scoutos-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

deploy

Deploy a new version of an app by providing its slug and the file contents to upload.

Instructions

Deploy a new version of an app

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": {
      "slug": "<slug>",
      "files": "<files>"
    },
    "name": "deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesApp slug
filesYesFiles to deploy (path -> content)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavior. 'Deploy a new version' implies a mutation (overwriting or creating a version), but it does not state side effects, whether it is idempotent, or if it triggers a build. This is minimal for a mutating tool.

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 a single, front-loaded sentence with no redundant words. It efficiently conveys the core action and resource.

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?

The tool's simplicity is not enough to compensate for missing behavioral context. In the absence of an output schema or annotations, the description does not explain return values, success/failure behavior, or whether deployment is synchronous. This leaves significant gaps for an AI 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 coverage is 100%, with both parameters described (slug as app identifier, files as path->content mapping). The description adds little beyond the schema, but the 'new version' phrase hints at the files' role without adding specific format details. 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 uses a specific verb (deploy) and resource (app), clearly indicating a deployment action. It is distinct from sibling tools like app_create (which creates an app) or logs (which retrieves logs), but does not explicitly call out the differences.

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 prerequisites or deployment scenarios mentioned. The description simply states what it does, leaving the agent to infer usage context from sibling names.

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