Skip to main content
Glama
dbe006

rugguard-mcp

by dbe006

explain_scan

Fetch detailed audit trail for any previous token scan to understand the reasoning behind its risk verdict. Use for compliance, post-mortems, or user-facing explanations.

Instructions

Fetch the per-heuristic audit trail of a previous scan.

Costs $0.005 USDC. Use this when you need to know why a scan returned a specific verdict — e.g. for compliance, post-mortems, or building a user-visible explanation.

Args: scan_id: UUID returned by a prior scan_token call.

Returns: On success: {scan_id, scanned_at, score, verdict, heuristic_results: [...]}. On failure: {error, message}. Same error codes as scan_token.

In demo mode: returns a canned audit trail keyed by the scan_id
suffix (`demo-safe-01`, `demo-caution-01`, `demo-critical-01`).
Unknown scan_ids return a demo-safe trail. Response has `_demo: true`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scan_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses cost, fetch-only nature, success/failure return formats, and demo mode behavior with `_demo: true`. Could mention rate limits or auth but covers key aspects.

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?

Well-structured: purpose, cost/usage, arguments, returns, demo mode – all in a few sentences. Front-loaded with purpose. No wasted words.

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?

Covers all necessary aspects for a simple tool: purpose, cost, return format (including error and demo), and source of scan_id. Output schema exists so return details are sufficient.

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?

Only one parameter (scan_id) with 0% schema coverage. Description adds value by stating it's a UUID from a prior `scan_token` call, providing source context beyond schema.

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?

Clearly states 'Fetch the per-heuristic audit trail of a previous scan' – a specific verb and resource. Distinguishes from sibling tools 'pretrade_check' and 'scan_token' by its post-scan audit purpose.

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?

Explicitly says when to use: 'Use this when you need to know *why* a scan returned a specific verdict — e.g. for compliance, post-mortems, or building a user-visible explanation.' Also mentions cost ($0.005 USDC). Does not explicitly state when not to use, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dbe006/rugguard-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server