Skip to main content
Glama

weavegraph_verify_merge

Verify 3-way merge safety across Base, Agent A, and Agent B file maps to detect silent semantic AST breaks such as signature changes, dangling imports, or duplicate definitions.

Instructions

Verify 3-way merge safety across Base, Agent A, and Agent B file maps for silent semantic AST breaks.

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": {
      "base_tree": "<base_tree>",
      "agent_a_tree": "<agent_a_tree>",
      "agent_b_tree": "<agent_b_tree>"
    },
    "name": "weavegraph_verify_merge"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_treeYes
agent_a_treeYes
agent_b_treeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 of behavioral disclosure. It adds useful context by naming 'silent semantic AST breaks,' but it does not state whether the operation is read-only, what the result looks like, or how the verification behaves on failure.

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 with no wasted wording. It communicates the core operation and the specific class of breakage being checked efficiently.

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 three required nested-object parameters, no annotations, and no output schema, the description is not complete enough for an agent to invoke the tool confidently. It omits the expected file-map structure, return behavior, and any safety or permission context.

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?

The description maps the three required parameters to Base, Agent A, and Agent B file maps, which adds some meaning beyond the bare object schema. However, schema description coverage is 0% and the parameters are nested objects, so the description does not explain the structure or expected contents of those file maps.

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 specific verb and resource: verifying 3-way merge safety across Base, Agent A, and Agent B file maps, specifically for silent semantic AST breaks. It is clear what the tool does, though it does not explicitly differentiate itself from the sibling tools.

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 implies the tool is used to verify merge safety, but it gives no explicit when-to-use guidance, no exclusions, and no alternatives among the sibling tools. An agent must infer the usage context from the purpose statement alone.

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