Skip to main content
Glama
concurrence-hq

forge-mcp

by concurrence-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

forge_scenario_create

Create a simulation scenario and its initial version by specifying objective, instructions, conversation start type, and timestamp.

Instructions

Create a new simulation scenario with its initial version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the simulation scenario
tagsYesTags (alphanumeric keys and values, no hyphens or special characters)
org_idNoOrg ID (uses active org if omitted)
initial_versionYesInitial version of the scenario

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.14
    • removedInput schema / properties / initial_version / properties / conversation_starts_at / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / initial_version / properties / conversation_starts_at / type
      Added value: +[
+  "string",
+  "null"
+]
  2. First observedv0.1.13

TDQS

A3.5/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 behavioral burden, but it only states that a scenario and initial version are created. It does not disclose side effects, org scoping behavior, required fields beyond the schematic plain reading, or what happens on success.

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?

A single front-loaded sentence delivers the core action and scope with no filler. Every word contributes to identifying what the tool does.

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 nested-object create with no output schema and no annotations, the high-level sentence plus the rich parameter schema is minimally sufficient, but it omits context like active-org behavior and result expectations. It is complete enough for a simple create but leaves behavioral gaps to inference.

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 description does not need to restate parameter meanings. The phrase 'initial version' only echoes the initial_version parameter and adds no semantic detail beyond the schema.

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

Purpose5/5

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

The description states a specific action ('Create') with a specific resource ('simulation scenario') and adds that it includes the 'initial version,' which clearly distinguishes it from the update-oriented sibling forge_scenario_update. The verb-resource pairing is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The wording implies this tool is for creating a scenario rather than updating one, but it never explicitly says when to choose it over forge_scenario_update or other create tools. No alternatives, prerequisites, or exclusions are mentioned.

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