Skip to main content
Glama
Marketing Ops MCP

Marketing Ops MCP

reconcile_transactions

Read-onlyIdempotent

Compare exact transaction IDs and amounts across two datasets only when attribution scopes match, applying a tolerance to flag mismatches for reconciliation.

Instructions

Compare exact transaction IDs only when declared attribution scopes match.

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": {
      "payload": "<payload>"
    },
    "name": "reconcile_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the exact-ID comparison and scope-match constraint; it does not disclose whether amounts or tolerance affect the comparison, what the result contains, or how mismatches are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no filler. Its terseness, however, becomes under-specification: the key phrase 'declared attribution scopes match' is not defined, so the sentence is concise but not self-sufficient.

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?

For a complex nested reconciliation payload with no output schema, the definition is far too thin. It omits the meaning of left/right inputs, how tolerance is applied, whether amounts are compared, and what the caller should expect back.

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%, and the nested payload includes left/right transaction arrays, a tolerance field, and full Scope objects. The description mentions transaction IDs and attribution scopes but says nothing about left versus right, amount comparison, tolerance semantics, date_basis, or lookback_days.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Compare') and resource ('exact transaction IDs'), plus a gating condition ('declared attribution scopes match'). However, it leaves the broader meaning of 'reconcile' unclear—whether it identifies missing IDs, compares amounts, or reports mismatches—and does not distinguish this tool from any alternative.

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?

It provides one precondition ('only when declared attribution scopes match') but no guidance on when to use this tool versus alternatives, how to determine whether scopes match, or what to do when they do not. The usage context is implied rather than explained.

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