Skip to main content
Glama

AutoTasker Hub — China Social Data API

settlement_history

Last N settlements from the ledger (tool, amount, payer, ts). $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": "settlement_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It helpfully discloses the return shape (tool, amount, payer, ts) and flags a cost of $0.01 USDC, but says nothing about ordering direction, pagination, authentication, or whether the call is read-only and safe to repeat.

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?

Two terse fragments with zero filler, and the core purpose is front-loaded. The trailing '$0.01 USDC' is useful cost disclosure though it reads as an unlabeled fragment.

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 one-parameter, no-output-schema tool the description is nearly sufficient: it names the fields returned and the cost. It falls short on ordering semantics ('last' by what field) and on the limit parameter's bounds and default, which no other structured field supplies.

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 coverage is 0% for the single `limit` parameter, so the description must compensate. 'Last N' meaningfully ties N to the count parameter, but it omits the default of 10 and the maximum of 50, leaving the agent to discover the schema.

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 specific resource and scope ('Last N settlements from the ledger') and enumerates the returned fields (tool, amount, payer, ts), so an agent knows exactly what it gets. It does not differentiate itself from the sibling wallet_history, which is the main gap.

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

Usage Guidelines2/5

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

There is no guidance on when to pick this over wallet_history or other history tools, and no stated prerequisites or exclusions. The only implied usage is 'fetch recent settlements,' which the agent must infer.

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.