Skip to main content
Glama
Sign In
Make MCP Server

Make MCP Server

by integromat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

run_scenario_11707

Trigger and interact with automation workflows by processing an array of text collections. Designed for integrating Make scenarios with AI systems to enhance task automation.

Instructions

Scenario Inputs: Array of Collections

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_scenario_11707"
  }
}

Input Schema

NameRequiredDescriptionDefault
arrayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to describe any behavioral traits—such as whether it's read-only or destructive, what permissions are needed, or what the tool outputs—making it impossible for an agent to understand how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

While concise with a single phrase, it's under-specified rather than efficiently structured. The description lacks essential information, making it ineffective—conciseness should not come at the cost of clarity, and this text fails to earn its place by adding value.

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

Completeness1/5

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

Given the complexity implied by 'run_scenario' and the lack of annotations, output schema, or schema descriptions, the description is completely inadequate. It doesn't explain the tool's purpose, behavior, parameters, or results, leaving critical gaps for agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, and the description only vaguely references 'Array of Collections' without explaining what 'Collections' are, what the 'text' property means, or how the array should be structured. It adds no meaningful semantics beyond the bare schema.

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 'Scenario Inputs: Array of Collections' is vague and tautological—it restates the parameter name ('array') without specifying what the tool actually does. It mentions 'Scenario' but doesn't define what a scenario is or what action 'run' entails, failing to distinguish it from sibling tools like run_scenario_11422.

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

Usage Guidelines1/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. The description offers no context, prerequisites, or exclusions, leaving the agent with no basis to choose between this and sibling tools like run_scenario_11652 or run_scenario_11704.

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

Related Tools