Skip to main content
Glama
Sign In

chaink9

by com.chaink9
OverviewDiscussionsAdmin

portfolio-screen

Read-only

Read actual wallet balances for up to twenty supplied token addresses on one chain and prioritize their stored ChainK9 scan verdicts. Includes scan age/staleness and missing reports. Does not discover wallet assets, run fresh scans or establish wallet-specific sellability; use exit-check for that. Costs $0.005 per successful call in USDC on Base, Polygon, Arbitrum, Avalanche, BNB Smart Chain (USDT) or Solana, paid with x402 in the call's _meta; failed calls are free.

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": {
      "wallet": "<wallet>",
      "tokens": "<tokens>"
    },
    "name": "portfolio-screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobsc (BNB Smart Chain, the default), eth (Ethereum) or base (Base)
tokensYesComma-separated token addresses, one to twenty
walletYesWallet whose balances to read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations it discloses pricing ($0.005 per successful call), the payment mechanism (x402 via the call's _meta), supported payment rails, and that failed calls are free. It also sets return-behavior expectations that annotations cannot convey: verdicts are stored (not fresh), scan age/staleness matters, and missing reports are surfaced.

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?

Purpose and scope come first, followed by a clear negative-scope sentence naming the alternative, then pricing. The closing payment sentence is long and enumerates several tokens and chains, but every element is operationally relevant since the agent must supply _meta payment details.

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?

For a read-only tool with no output schema, the description still conveys what comes back (balances plus prioritized stored verdicts, scan age, missing reports) and what the agent must supply out-of-band (x402 payment in _meta). Nothing needed to call it correctly or interpret results appears absent.

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 100%, so chain, tokens and wallet are already well documented in the schema, including the one-to-twenty token constraint. The description reinforces the 'one chain' and 'up to twenty' framing but adds no format or syntax detail beyond that. The payment-chain list (Polygon, Arbitrum, Avalanche, Solana, etc.) does not match the query-chain enum (bsc/eth/base/arc), which could momentarily confuse which chain list applies to the call.

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 concrete verb and resource: reads wallet balances for up to twenty supplied token addresses on one chain and prioritizes stored ChainK9 scan verdicts for those tokens. It also explicitly delimits scope against siblings ("Does not discover wallet assets, run fresh scans..."), so an agent can tell this apart from scan/verdict/exit-check without opening schemas.

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

Usage Guidelines5/5

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

Explicitly names what the tool does not do (no asset discovery, no fresh scans, no wallet-specific sellability) and routes that need to exit-check, which is the sibling for sellability. The input side is also constrained (supplied addresses only, one chain, max twenty), so the when-to-use condition is unambiguous.

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

All chaink9 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