Skip to main content
Glama

audit_smart_contract_escrow

Idempotent

[Private] Is this Solidity contract safe? Compiles it and flags selfdestruct, unsafe delegatecall, tx.origin phishing and missing functions. Example: contractName='VaultToken'.

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": {
      "soliditySourceCode": "<soliditySourceCode>"
    },
    "name": "audit_smart_contract_escrow"
  }
}

Input Schema

NameRequiredDescriptionDefault
contractNameNoTarget contract name inside the Solidity source.
requiredFunctionsNoFunction names that must exist in the compiled ABI.
soliditySourceCodeYesComplete Solidity smart contract source code to compile and scan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / contractName / description
      Added value: +"Target contract name inside the Solidity source."
    • addedInput schema / properties / contractName / examples
      Added value: +[
      +  "VaultToken"
      +]
    • addedInput schema / properties / requiredFunctions / description
      Added value: +"Function names that must exist in the compiled ABI."
    • addedInput schema / properties / soliditySourceCode / description
      Added value: +"Complete Solidity smart contract source code to compile and scan."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, idempotent=true, openWorldHint=false; the description adds real substance by enumerating the exact vulnerability classes checked (selfdestruct, unsafe delegatecall, tx.origin phishing, missing functions) and disclosing that the source is actually compiled. It omits whether the tool costs anything, how long compilation takes, and what a result looks like, and the '[Private]' prefix is unexplained.

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?

A single compact sentence front-loads the core question, then the mechanism, then the checks, followed by a concrete parameter example. Nothing is padded. The only mild inefficiency is the unexplained '[Private]' tag, which consumes attention without conveying actionable meaning.

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

Completeness3/5

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

With no output schema, the description carries the burden of explaining return values, and it only says the tool 'flags' issues without indicating structure, severity, or whether compilation errors are reported separately. It does cover the input side well and names the checks performed. Adequate to call correctly, but an agent cannot predict what it will receive back.

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 all three parameters are already documented in the schema, which sets the baseline at 3. The description only reinforces contractName via an example and hints at requiredFunctions through the phrase 'missing functions' without explaining the ABI-membership semantics. It adds no new meaning beyond the schema.

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?

States a specific verb and resource: compiles a Solidity contract and flags selfdestruct, unsafe delegatecall, tx.origin phishing, and missing functions. The resource (Solidity source) plus the tool name cleanly separates it from the other audit_*_escrow siblings, which target different artifact types. It stops just short of explicitly naming a sibling alternative, which keeps it at 4 rather than 5.

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?

Usage is implied by the opening question 'Is this Solidity contract safe?' and by the list of checks, so an agent can infer this is a pre-deployment static security scan of Solidity source. There is no explicit when-to-use vs when-not guidance, no prerequisites, and no statement about what to do if compilation fails or if the agent should prefer a different audit tool.

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.