Skip to main content
Glama

Merge Card Bridge

card_confirm_merge
Destructive

Internal bridge for the merge card's Merge button (not for agents).

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": {
      "jobId": "<jobId>",
      "secret": "<secret>"
    },
    "name": "card_confirm_merge"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
secretYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=false, so the safety profile is covered. The description adds the useful context that this is an internal UI bridge rather than an agent-facing operation, which explains the destructive nature. It says nothing about what the merge does to state, whether it can be undone, or how the 'secret' credential is obtained.

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?

A single short sentence, front-loaded with the identity of the tool and immediately followed by the exclusion. Nothing superfluous.

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

Completeness3/5

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

For a two-parameter internal bridge with no output schema, the description supplies the one thing that matters most: it is not intended for agent use. It still omits what the call actually does and how the secret is sourced, so an agent cannot reason about it beyond avoiding it.

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% for both required parameters, so the description carries the full burden and it does not compensate. Neither 'jobId' (presumably a merge job) nor 'secret' (presumably an internal auth token) is explained, leaving an agent with no idea how to supply valid values — though the 'not for agents' note makes that moot in practice.

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 names the concrete thing this tool serves — the merge card's Merge button — plus the title 'Merge Card Bridge', so an agent can identify it as a UI-triggered merge operation rather than a general-purpose merge tool. It lacks an explicit verb+resource statement of what the bridge actually performs (e.g., commits the merge for a job), which keeps it below a 5.

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?

It gives an explicit exclusion — '(not for agents)' — which is exactly the routing signal an agent needs to avoid calling it. It does not name a sibling to use instead for actual merge work, so it stops short of full when/when-not/alternative guidance.

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