Skip to main content
Glama

Get Merge Status

get_merge_status
Read-only

State of a merge by mergeId (merges started in the UI too): running, done or failed. On failed: the failing step or migration script and its exact error. On done: the keys added to the target and the passed pre-merge checks.

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": {
      "mergeId": "<mergeId>"
    },
    "name": "get_merge_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
mergeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description goes beyond them by disclosing the shape of the response per state: failing step or migration script with the exact error on failure, and added keys plus passed pre-merge checks on success. It does not say whether states are terminal or how long results persist.

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?

Three short sentences, front-loaded with the resource and state list, then the failure payload, then the success payload. No filler, and the most decision-relevant detail (running/done/failed) comes first.

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?

With no output schema, the description must explain returns and does so at a useful level of detail, including error content. It falls slightly short on operational context an agent polling a merge might need, such as whether status is eventually consistent or whether the record expires.

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

Parameters4/5

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

Schema coverage is 0% for the single mergeId parameter, so the description must carry the burden. It clarifies that mergeId refers to a merge record including ones initiated in the UI, which meaningfully narrows what identifier is acceptable, though it gives no format guidance (e.g., where the ID comes from).

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?

States a specific resource and scope: 'State of a merge by mergeId', and enumerates the possible outcomes (running, done, failed). The parenthetical '(merges started in the UI too)' pre-empts a likely misreading about scope, so an agent can tell this apart from get_job_status or get_publish_status by resource type alone.

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?

Usage is only implied: an agent can infer this is the polling companion to start_merge/card_confirm_merge, but the description never says when to call it, how often, or what to do instead if the mergeId is unknown. The UI-merge scoping note is the only explicit boundary it draws.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources