Skip to main content
Glama
ReportProof MCP Server

ReportProof MCP Server

by vikyathhj-ui

check_report

Verifies every number in a draft marketing report against source data from GA4, Google Ads, Meta Ads, Search Console, CSV or JSON, returning PASS or FAIL with each discrepancy and closest real value.

Instructions

Check every number in a draft marketing report against the source data. Returns PASS, or FAIL with each wrong number, its line, the problem (not in data / wrong direction) and the closest real value. Use after writing a report from GA4, Google Ads, Meta Ads or Search Console data; rewrite only the flagged sentences and check again.

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": {
      "report": "<report>"
    },
    "name": "check_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoCurrent period end, YYYY-MM-DD.
dataNoJSON sources: [{name, rows}] with plain row objects, [{name, ga4_report}] with a GA4 runReport response unchanged, or [{name, google_ads}] with a Google Ads search/searchStream response unchanged.
filesNoCSV exports: [{name, content}] (content = CSV text). Use content_base64 for UTF-16 files.
goalsNoTargets, e.g. {"conversions": 150, "cpa@blended": 40}.
startNoCurrent period start, YYYY-MM-DD. Omit to use the latest complete month.
reportYesThe draft report text.
compareNoCompare with the previous period (default) or the same period last year.
currencyNo3-letter currency code if the data doesn't say, e.g. USD or INR.
number_styleNoindian = lakh/crore grouping.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does substantial work: it discloses the return contract (PASS, or FAIL with each wrong number, line, problem classification, and closest real value) and the nature of the operation (non-mutating checking). It does not discuss permissions, limits, or how source data is matched when ambiguous, so a 4 rather than a 5.

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?

Two tightly packed sentences with the core action first and the return contract second; every clause earns its place and there is no filler.

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 9-parameter tool with nested objects and no output schema, the description compensates by explaining PASS/FAIL return semantics and the iterate-and-recheck workflow. It leaves some ambiguity about how multiple data sources are reconciled and what 'wrong direction' means precisely, but the essentials for correct invocation are present.

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

Parameters3/5

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

Schema description coverage is 100%, including detailed descriptions of the data/files shapes and enum meanings for compare and number_style, so the baseline is 3. The description adds no parameter-level detail beyond the schema – it never mentions start/end, goals, currency, or number_style.

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?

States a specific verb and object: 'Check every number in a draft marketing report against the source data.' An agent immediately knows this validates numbers against sources. However, it does not distinguish itself from the sibling 'verify_report', which by name sounds like the same function, so a 4 rather than 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?

Gives concrete context and ordering: 'Use after writing a report from GA4, Google Ads, Meta Ads or Search Console data' plus the remediation loop 'rewrite only the flagged sentences and check again.' No explicit exclusions or named alternatives among siblings, so not a 5.

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

Deploy Server

Other Tools