zaytsv-bot-graph-mcp

rename_graph

Rename a graph scenario to a new name, even if published. The name change does not affect execution.

Instructions

Переименовать сценарий (работает и для опубликованных — имя не влияет на исполнение).

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": {
      "graphId": "<graphId>",
      "name": "<name>"
    },
    "name": "rename_graph"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`graphId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.0Aug 10, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It adds a meaningful trait: renaming published scripts does not affect execution. However, it omits other potential behaviors like idempotency, permission requirements, or side effects, making this only minimally adequate.

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, front-loaded sentence that is concise and directly states the purpose and a key caveat. No wasted words.

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

Completeness4/5

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

For a simple two-parameter tool with no output schema, the description covers the most relevant context (published scripts, execution impact). It leaves out some operational details, but is reasonably complete given the low complexity.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It does not explain the parameters beyond what the schema shows (graphId and name), nor does it add details like uniqueness constraints or format expectations. The meaning is largely inferred from the tool name.

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 clearly states the action: 'Rename a script' (Переименовать сценарий), which maps directly to the tool name rename_graph. It adds a specific nuance (works for published ones) that distinguishes it from broader tools like update_graph.

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

Usage Guidelines4/5

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

The description provides clear usage context by noting that the tool works for published scripts and that renaming does not affect execution. It implies a safe use case but does not explicitly name alternatives or exclusions, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.