Skip to main content
Glama
Sign In
google-meridian-mcp

google-meridian-mcp

by muhammad1azmi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_mmm_workflow_guide

Use decision trees and iteration rules to navigate modeling phases and iteration loops in Marketing Mix Modeling.

Instructions

Provides decision trees and iteration rules for modeling phases and iteration loops.

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

Input Schema

NameRequiredDescriptionDefault
phaseNophase1_data_prep, phase2_specification, loop_a_convergence, loop_b_plausibility, loop_c_calibration, phase4_optimization, or ALLALL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/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. It only states it provides information, but does not disclose potential side effects, required permissions, or other behavioral traits.

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, focused sentence with no unnecessary words. It efficiently communicates the core function.

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?

The description provides minimal context. It does not explain the structure of the output, the range of phases, or how the decision trees are organized. While the parameter definition helps, the overall completeness is adequate but not thorough.

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% (the single parameter phase has a description listing valid values). The tool description does not add any additional meaning 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 that the tool provides decision trees and iteration rules for modeling phases and iteration loops, which is a specific verb+resource. However, it does not elaborate on what 'modeling phases' specifically refer to, nor does it differentiate from sibling tools like get_control_point_guide.

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 offers no guidance on when to use this tool versus alternatives (e.g., fetch_docs, get_control_point_guide). It lacks any context about prerequisites, typical scenarios, or when not to use it.

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