Skip to main content
Glama
Sign In
DirectAI MCP

DirectAI MCP

by perejaslav
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

plan_write

Prepare a write plan with preview, warnings, and plan ID to validate Yandex Direct campaign changes before execution.

Instructions

Подготовить запись: предпросмотр, предупреждения, plan_id.

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": {
      "name": "<name>",
      "params": "<params>"
    },
    "name": "plan_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It conveys that the tool produces a preview and warnings rather than directly applying a change, which is useful, but it does not explicitly state side-effect safety, authorization needs, or failure behavior.

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?

A single compact sentence front-loaded with the verb and key artifacts. There is no filler or repetition, although the brevity comes at the cost of missing input guidance.

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?

The output schema likely covers return values, but the description is otherwise incomplete: it does not explain what name/params mean, how the plan connects to apply_write, or any preconditions. For a tool with a free-form params object, this is too thin.

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 coverage is 0% and the description adds no meaning to 'name' or 'params'. 'params' is an open object with no documented keys, and 'name' could be an action identifier or something else; an agent cannot reliably construct valid input. The only related term, plan_id, appears as an output artifact, not an input.

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 states a concrete operation ('prepare a write') and names the artifacts it produces (preview, warnings, plan_id). This distinguishes it at the intent level from apply_write, though it never explicitly names the sibling.

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 verb 'prepare' plus preview/warnings/plan_id implies this is a pre-flight step before apply_write rather than an actual mutation. However, it never explicitly states when to use it vs. alternatives 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