Skip to main content
Glama
ReportProof MCP Server

ReportProof MCP Server

by vikyathhj-ui

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RAPIDAPI_KEYYesYour ReportProof (RapidAPI) API key, required to call the ReportProof API. The free plan (50 calls/month) is available at rapidapi.com/VikyathJ/api/reportproof.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Use compute_metrics for exact marketing numbers and check_report to verify every number in a drafted report before sending it.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_reportA

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.

compute_metricsA

Compute exact report metrics from marketing data: totals, % change vs previous period or last year, CTR, CPC, CPA, ROAS and rates recomputed from totals (never averaged), blended ad totals, goal progress, top movers and anomalies, with ready-to-print display strings. Use these numbers when writing a report.

verify_reportB

Verify a draft report against a metrics object previously returned by compute_metrics.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation3/5

check_report and verify_report both validate a draft report and differ only in data source (raw source data vs. a metrics object from compute_metrics), which is a subtle boundary an agent can easily cross. The descriptions do state when to use each, but the near-synonymous names 'check' and 'verify' increase misselection risk. compute_metrics is clearly distinct.

Naming Consistency5/5

All three tools follow a clean verb_noun snake_case pattern: check_report, verify_report, compute_metrics. The convention is uniform and predictable, even if check/verify are semantically close.

Tool Count4/5

Three tools is a tight, well-scoped surface for a narrow report-proofing purpose. However, check_report and verify_report are close enough that one could arguably be folded into the other, making the set feel slightly redundant rather than minimal.

Completeness4/5

The compute-then-verify/check lifecycle covers the core workflow: derive exact metrics, then validate a draft against either raw data or computed metrics. Minor gaps exist (e.g., no way to fetch or inspect the source data itself, or to re-check only flagged lines), but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues