Skip to main content
Glama

BRAINIAC Fleet Fuel Card Controls

Detect fuel card abuse

fleet-operations_fuel-card-abuse-detect

Flag fuel card transactions that exceed tank capacity, mismatch fuel type, duplicate within a time window, share one card across vehicles, overflow the tank without mileage burn evidence, or appear too far from the vehicle for the supplied max speed. Volumes are millilitres. Every flag includes deterministic evidence. No telematics or merchant network is queried. Price $0.04 USDC. POST /api/v1/fleet-operations/fuel-card-abuse-detect. Unpaid calls return 402 and do not run.

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": {
      "vehicles": "<vehicles>",
      "transactions": "<transactions>"
    },
    "name": "fleet-operations_fuel-card-abuse-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
vehiclesYes
locationsNo
transactionsYes
odometer_readingsNo
duplicate_window_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses meaningful behavior: every flag includes deterministic evidence, no external telematics or merchant network is queried, the call costs $0.04 USDC, and unpaid calls return 402 without running. It does not cover authorization requirements, idempotency, or the detailed return shape.

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

Conciseness4/5

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

The description is front-loaded with the detection scope and each sentence adds relevant information: units, evidence, external data exclusions, price, endpoint, and payment failure behavior. It is dense but not wasteful, though bullet points could improve scanability.

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 tool with five parameters, nested arrays, no annotations, and no output schema, the description explains the detection logic and payment behavior but leaves gaps around the exact return structure and full parameter roles. It is adequate as a minimum but not complete for an agent that needs to construct the request precisely.

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 0%, so the description must compensate. It adds important meaning such as 'Volumes are millilitres' and ties detection rules to parameters like max speed, tank capacity, fuel type, and a duplicate time window, but it does not explain the five top-level parameters or the optional locations and odometer datasets in detail.

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 uses a specific verb ('Flag') and resource ('fuel card transactions') and enumerates the exact abuse conditions detected: tank capacity, fuel type mismatch, duplicates, shared cards, overflow without mileage, and distance/speed inconsistency. An agent can immediately tell what the tool does.

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 clearly scopes the tool to supplied data by stating 'No telematics or merchant network is queried,' which tells the agent when this tool is appropriate versus tools that require external integrations. Pricing and the 402 behavior also inform invocation, though there are no sibling alternatives to compare against.

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