Skip to main content
Glama
Sign In

fia-signals-mcp

by io.github.Odds7
OverviewDiscussionsAdmin

pre_trade_risk_batch_checkout

Alias for token_safety_batch_checkout using the /pre-trade-risk/batch buyer-facing path. Metadata only; no payment is made.

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": {
      "token_addresses": "<token_addresses>"
    },
    "name": "pre_trade_risk_batch_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase
token_addressesYesComma-separated EVM token addresses, maximum 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that no payment is made and it is metadata-only, which is useful. However, it does not mention auth requirements, rate limits, or any other side effects.

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?

The description is a single sentence that is direct and front-loaded. It communicates the alias relationship, the path, and the metadata-only nature without any wasted words.

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

Completeness2/5

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

The tool has no output schema and the description does not describe what the tool returns. Being an alias, it relies entirely on the referenced token_safety_batch_checkout, which is not defined here, leaving the agent without complete context for expected outputs or behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (token_addresses has a description, chain does not). The description adds no parameter information at all, so it does not compensate for the missing chain description and provides no extra meaning beyond 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 states it is an alias for token_safety_batch_checkout using a specific buyer-facing path, and clarifies it is metadata-only with no payment. This provides a clear sense of the operation, though it doesn't explicitly describe the underlying risk-checking function.

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?

It mentions the buyer-facing path but provides no explicit guidance on when to use this tool versus the original token_safety_batch_checkout or other siblings. There are no stated exclusions or alternative scenarios.

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

All fia-signals-mcp 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