Skip to main content
Glama
Sign In

Prax Data Services

by com.orabrain
OverviewDiscussionsAdmin

Screen transfers (batch)

screen_transfers_batch
Read-onlyIdempotent

Bulk transfer screening: screen_transfer for up to 50 transfers in one call (items of {from, to, amount, asset, chain}) - payout batches, payroll, exchange withdrawals. Returns a verdict per item and a summary. Builder plan and above; 10 credits per call.

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": {
      "items": "<items>"
    },
    "name": "screen_transfers_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the bar is lower. The description adds genuinely new operational context: the per-item verdict plus summary return shape, a plan gate ('Builder plan and above'), and a cost ('10 credits per call') that matters for batching decisions.

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?

One front-loaded sentence carries purpose, payload shape, use cases, return shape, and cost. No filler, no restatement of the title, and the sibling relationship is embedded rather than belabored.

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?

With no output schema, the description still describes the return (verdict per item plus summary), and it covers limits, plan gating, pricing, and item fields. For a one-parameter tool with an opaque array schema, this is enough to call it correctly.

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?

Schema coverage is 0% and the items array is an untyped object, so the description is the only documentation of the payload shape. It supplies the exact item fields {from, to, amount, asset, chain} and the 50-item cap, though it says nothing about field formats, required subfields, or valid chain/asset values.

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?

States a specific verb and resource ('Bulk transfer screening') plus the scope that separates it from the single-item sibling: 'screen_transfer for up to 50 transfers in one call'. An agent can distinguish batch from single screening without opening either schema.

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?

Gives concrete use cases (payout batches, payroll, exchange withdrawals) that tell the agent when to reach for the batch variant, and the 'up to 50 in one call' phrasing implies the single-item alternative. It stops short of an explicit 'use screen_transfer for one item' exclusion.

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

All Prax Data Services 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