Skip to main content
Glama

ChainGuard Web3 & MCP Shield

audit_solidity_or_mcp

Instant triage audit of Solidity contracts or MCP/AI agent configs for vulnerabilities & token burn.

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": {
      "content": "<content>"
    },
    "name": "audit_solidity_or_mcp"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
target_typeNoauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says the tool performs an "instant triage audit" and targets vulnerabilities and token burn, but it does not state whether the operation is read-only, whether content is executed or statically analyzed, what permissions are needed, or what the output looks like.

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 a single front-loaded sentence with no filler. It is appropriately sized for the amount of information provided, though "token burn" is ambiguous and could use a brief clarification.

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?

There is no output schema and no annotations, and the parameters have 0% schema coverage. For an audit tool with two target domains, the description is too thin: it omits expected inputs, return behavior, limitations, and how it relates to the more specific sibling audit tools.

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 description coverage is 0%, so the description must compensate for the two undocumented parameters. It implies there are multiple target categories (Solidity contracts and MCP/AI agent configs), but it does not explain what the content parameter should contain or what values target_type accepts, including the auto default.

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 a specific action (triage audit) and resource (Solidity contracts or MCP/AI agent configs), and names the issues it looks for (vulnerabilities and token burn). It is clearer than a tautology, but it does not explicitly distinguish itself from the specialized sibling checks.

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?

The word "triage" implies this is a preliminary broad scan, giving some implicit usage guidance. However, there is no explicit instruction on when to use this versus the targeted sibling tools such as check_mcp_poisoning or check_eip7702_delegation, and no exclusions are stated.

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.

Resources