Skip to main content
Glama

maxmind-minfraud

by io.usefulapi
OverviewDiscussionsAdmin

Report a transaction outcome

minfraud_report_transaction
Destructive

WRITE — submits fraud feedback to MaxMind. Report the real-world outcome of a transaction (e.g. it was a chargeback or confirmed fraud) so minFraud can improve future scoring. This mutates MaxMind's model of your traffic; it is not a read. Requires a tag and at least one identifier (ip_address, maxmind_id, minfraud_id, or transaction_id). API: POST /minfraud/v2.0/transactions/report (returns HTTP 204).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYesREQUIRED. The outcome you are reporting for this transaction.
notesNoFree-form notes about the transaction.
ip_addressNoIdentifier: the IP address of the reported transaction.
maxmind_idNoIdentifier: the 8-character maxmind_id from a prior response.
minfraud_idNoIdentifier: the minfraud_id (UUID) from a prior response.
transaction_idNoIdentifier: your own transaction_id sent at scoring time.
chargeback_codeNoThe chargeback reason code, if tag=chargeback.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description reinforces the destructiveHint annotation by stating 'mutates MaxMind's model' and 'not a read'. It also specifies the API endpoint and HTTP 204 response, providing context beyond annotations.

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?

Four sentences, front-loaded with 'WRITE' and a clear purpose. Every sentence contributes essential information without redundancy.

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

Completeness5/5

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

For a mutation tool without output schema, the description covers input requirements, side effects, and API details comprehensively. No gaps remain.

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?

With 100% schema coverage, the description still adds value by summarizing required identifiers and clarifying chargeback_code usage. It explains parameter relationships not obvious from schema alone.

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?

The description explicitly says 'submits fraud feedback' and 'Report the real-world outcome', clearly distinguishing this write operation from sibling tools (which are read/analysis). The verb+resource combination is specific and unambiguous.

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?

The description states the tool is for reporting real-world outcomes and labels it 'WRITE', implying it should not be used for scoring/insights. However, it lacks explicit when-not-to-use or alternative mentions.

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

All maxmind-minfraud toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources