Skip to main content
Glama
Sign In
Launch Engine

Launch Engine

by ZionHopkins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

passive_deploy

Read-only

Scores marketplace assets and generates build specifications for passive deployment using a given market pipeline slug.

Instructions

Passive Asset Deployment Agent (PADA) — marketplace asset scoring and build specs.

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": {
      "market_name": "<market_name>"
    },
    "name": "passive_deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
market_nameYesThe market/pipeline slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations show readOnlyHint=true, but the description adds minimal behavioral context. It mentions 'scoring and build specs' but does not explain the output format, side effects, or permissions required. No contradiction with annotations.

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 one short sentence, lacking substance. While concise, it fails to provide necessary detail, making it under-specified rather than efficiently informative.

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 simple input and no output schema, the description should explain what 'scoring and build specs' entails. It is incomplete, leaving the agent uncertain about the tool's purpose and output.

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% for a single parameter 'market_name' described as 'The market/pipeline slug'. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'marketplace asset scoring and build specs' is vague; it does not clearly state what the tool does beyond passive deployment. The name suggests deployment, but the description focuses on scoring and specs, creating confusion.

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 usage guidelines are provided; the description does not indicate when to use this tool over siblings like 'deploy', 'passive_check', or 'passive_portfolio'. Missing context on prerequisites or alternatives.

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