Skip to main content
Glama
Sign In

chaink9

by com.chaink9
OverviewDiscussionsAdmin

risk-changes

Read-only

Compare the latest two stored ChainK9 scans. Returns changed, added and removed module results plus report timestamps. Does not run a new scan or independently verify implementation changes. Requires two saved scans; 404 is not charged. Costs $0.002 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": {
      "token": "<token>"
    },
    "name": "risk-changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobsc (BNB Smart Chain, the default), eth (Ethereum) or base (Base)
tokenYesToken with at least two stored scans on that chain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, it discloses pricing, payment networks, x402 payment via _meta, that 404 responses are not charged, and that failed calls are free. It also states the return shape and that the tool only compares stored results rather than verifying implementation changes.

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?

The description is front-loaded with purpose and return values, then constraints and cost. It is efficient overall, though the payment-network sentence is dense and the failure-billing idea is repeated in slightly different forms.

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 paid read-only comparison tool with no output schema, the description covers the return contents, prerequisites, non-goals, error charging behavior, and payment mechanics. An agent has enough information to decide whether and how to invoke it.

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 description coverage is 100%, so the token and chain parameters are already documented in the schema. The description reinforces that the token needs at least two saved scans, but adds no syntax or semantic detail beyond the schema and does not clarify the schema's arc enum value.

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?

The description states a specific verb and resource: compare the latest two stored ChainK9 scans. It also clarifies scope by saying it does not run a new scan, which distinguishes it from scan/scan-lite/scan-ultra siblings.

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?

It clearly says the tool requires two saved scans and does not run a new scan or independently verify implementation changes. It does not explicitly name the sibling tool to use when no saved scans exist, but the when-not-to-use condition is clear.

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