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

google-meridian-mcp

by muhammad1azmi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

synthesize_meridian_code

Generate clean, portable Python code for Google Meridian to run marketing mix models across any cloud environment.

Instructions

Synthesizes clean, portable, cloud-agnostic Python code for Google Meridian.

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

Input Schema

NameRequiredDescriptionDefault
config_jsonNo{}
pipeline_stageNoFULL_PIPELINE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

The description does not disclose behavioral traits such as output format, side effects, or dependencies. With no annotations, the description fails to provide necessary context for safe invocation.

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 extremely concise with a single sentence, but it is too brief to be effective. It earns its place but lacks structure and substantive content.

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 complexity (no output schema, only two parameters), the description is incomplete. It does not explain return values, expected input format, or how the tool integrates with siblings.

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?

Schema description coverage is 0%, and the description adds no information about the two parameters (config_json, pipeline_stage). It does not compensate for the lack of schema descriptions.

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 synthesizes Python code for Google Meridian, and it distinguishes from sibling tools like fetch_docs and list_doc_sources which are about documentation. However, it could be more specific about what 'synthesize' entails.

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 guidance is provided on when to use this tool versus alternatives, nor any context on prerequisites or limitations. The description lacks any usage instructions.

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