Skip to main content
Glama

arcanumfleet-mcp-server

ArcanumFleet Code & Contract Security Audit

arcanum_code_audit
Read-onlyIdempotent

Use this to run a fast, 0-API-key security review on a code or smart-contract snippet (flags reentrancy, authority leaks, and logic bugs). Costs 0.001 USDC via x402.

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": {
      "code": "<code>"
    },
    "name": "arcanum_code_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesSource code or smart-contract snippet to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds real context beyond that: it discloses the cost (0.001 USDC via x402) and the 'no API key' property, which an agent needs before invoking a paid endpoint. It stops short of explaining how the payment is authorized or how long an audit takes.

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?

Two short sentences, purpose front-loaded before the cost note, with no filler or repetition. Every clause carries information an agent can act on.

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

Completeness4/5

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

For a one-parameter analysis tool with no output schema, the definition covers what it does, what it flags, and what it costs. The remaining gap is what the result looks like — a structured report versus prose findings — which matters because no output schema exists to fill that in.

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?

With a single required parameter and 100% schema description coverage, the schema already documents 'code' fully. The description's phrase 'code or smart-contract snippet' slightly enriches the accepted input domain but adds no format, size, or language constraints — baseline 3 for high schema coverage.

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 pairs a specific verb ('run a ... security review') with a concrete resource ('a code or smart-contract snippet') and lists the defect classes it flags (reentrancy, authority leaks, logic bugs). That is far more informative than a name restatement, but it never distinguishes itself from the sibling 'arcanum_audit', which an agent could easily confuse with this tool.

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

Usage Guidelines3/5

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

'Use this to run a fast, 0-API-key security review' gives an implied usage context, and 'code or smart-contract snippet' scopes the input domain. However, there is no when-not-to-use guidance and no named alternative (e.g. arcanum_audit) for cases where this tool is the wrong choice.

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.