Skip to main content
Glama

AutoTasker Hub — China Social Data API

fraud_report

Latest fraud detection report: alarms, blocked wallets, suspicious patterns. $0.01 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fraud_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the important non-obvious trait that the call costs $0.01 USDC, which is genuinely useful. However, it says nothing about freshness/latency of the "latest" snapshot, whether results are cached or live, or whether payment/credentials are required before invocation — the main risks for an agent calling this.

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 short fragments, front-loaded with the resource and its contents, followed by the price. Nothing is wasted and nothing relevant is buried.

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 zero-parameter, no-output-schema snapshot tool, the description covers what the report contains and its cost, which is close to everything an agent needs to decide and call. The remaining gap is the absence of any note on how fresh or how large the returned report is.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not need to compensate for any schema gaps here.

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?

The description names the resource and its content precisely: "Latest fraud detection report: alarms, blocked wallets, suspicious patterns." An agent can tell it retrieves a snapshot report rather than performing detection or filtering. It stops short of a full verb phrase (no explicit "returns"/"fetches"), but the intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word "Latest" implies this is a no-argument snapshot call, and the listed content categories hint at when it is useful (checking fraud alarms/blocked wallets). There is no explicit when-to-use or when-not-to-use statement, but the sibling list contains no plausible competing tool, so the guidance gap is low-stakes.

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.