Skip to main content
Glama

BRAINIAC Crypto Security

Audit proxy upgrade storage

crypto-security_proxy-upgrade-storage-audit

Compare the Solidity storage layout of an upgradeable implementation with a proposed replacement. Variables are matched by slot and offset, not by name. The types map is used for structs, mappings, dynamic arrays, and byte sizes. compatibility_status is compatible, incompatible, warnings, or indeterminate. risk_level is low, medium, high, or critical. A compatible result is not a claim that the upgrade is safe. No chain is queried. Price $0.05 USDC. POST /api/v1/crypto-security/proxy-upgrade-storage-audit. Unpaid calls return 402 and do not run.

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": {
      "current": "<current>",
      "proposed": "<proposed>"
    },
    "name": "crypto-security_proxy-upgrade-storage-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
currentYes
proposedYes
proxyPatternNo
currentMetadataNo
proposedMetadataNo

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?

With no annotations, the description carries the behavioral load well: it discloses that no chain is queried, that unpaid calls return 402 without running, the price, the HTTP endpoint, and the enumeration of compatibility_status and risk_level values. It does not cover rate limits or confirm read-only idempotence explicitly, so it falls short of a 5.

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?

Front-loaded with the operation, then the matching rule, then result semantics, then the disclaimers and commercial terms. Nearly every sentence earns its place; the enum listings are arguably schema-duplicative but serve as the only disclosure of return values given no output schema.

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?

For a complex nested-input tool with no output schema and no annotations, the description covers result semantics and the payment/no-chain behavior but omits the shape of the actual response (per-variable findings, warnings) and the role of three of five parameters, so an agent still has gaps before invoking 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 0% across five parameters including deeply nested objects, so the description must compensate. It does explain the storage/offset matching semantics and the purpose of the types map (structs, mappings, dynamic arrays, byte sizes), but says nothing about proxyPattern, currentMetadata, or proposedMetadata, leaving meaningful gaps.

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?

Specific verb and resource: compares Solidity storage layout of an upgradeable implementation against a proposed replacement, and states the core matching rule ('matched by slot and offset, not by name'). That is enough to distinguish it from slot-grading or transaction-intent siblings without opening the schema.

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 context of use (pre-upgrade layout compatibility check) is implied by the first sentence and the caveat 'A compatible result is not a claim that the upgrade is safe' usefully bounds interpretation. But there is no explicit when-to-use vs when-not-to-use guidance and no named alternative sibling for adjacent questions such as slot grading.

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