Skip to main content
Glama
Sign In
Launch Engine

Launch Engine

by ZionHopkins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

validate_decide

Read-only

Decide whether to advance, iterate, or kill a market validation after evaluating the window results.

Instructions

Validation Verdict Engine — end-of-window decision: ADVANCE, ITERATE, or KILL.

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": "validate_decide"
  }
}

Input Schema

NameRequiredDescriptionDefault
market_nameYesThe market/pipeline slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe read-only behavior. The description adds that the tool outputs a decision among three categories, which is helpful but does not expand on other behavioral traits (e.g., response format, side effects). 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.

Conciseness4/5

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

The description is a single, well-structured sentence that front-loads the core concept. It is highly concise with no redundant information, though it could expand slightly to improve completeness without becoming verbose.

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 simple read-only tool with one parameter and no output schema, the description provides the essential purpose and decision options. However, it omits what the tool returns (e.g., a string, an object, a status), which is necessary since no output schema exists. This gap reduces completeness.

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 one parameter (market_name) already described as 'The market/pipeline slug'. The description does not add any additional meaning or formatting guidance beyond the schema, so 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?

The description clearly states the tool is a 'Validation Verdict Engine' for making an 'end-of-window decision' with three explicit options (ADVANCE, ITERATE, KILL). However, it does not differentiate from sibling tools like validate_check or validate_prep, which have similar names and potentially overlapping purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. The phrase 'end-of-window decision' implies a specific context but does not clarify prerequisites, exclusions, or relationships to sibling tools.

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