Skip to main content
Glama

BRAINIAC Crypto Security

Grade proxy storage slot changes

crypto-security_storage-slot-grade

Compare two caller-supplied storage layouts by slot, offset, and size. A name that moves is a shift. Different names that occupy the same bytes are a collision. The grade and the collision score come from those counts. A variable is one slice of a single slot. No chain is queried. Price $0.04 USDC. POST /api/v1/crypto-security/storage-slot-grade. 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": {
      "previous": "<previous>",
      "next": "<next>"
    },
    "name": "crypto-security_storage-slot-grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextYes
previousYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses that no chain is queried, the price ($0.04 USDC), the transport (POST /api/v1/crypto-security/storage-slot-grade), and the failure behavior (unpaid calls return 402 and do not run). The main remaining gap is that the possible grade values and collision-score range are never spelled out.

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?

Short declarative sentences, front-loaded with the core operation before the definitions, pricing, and endpoint. Every sentence adds a usable fact: semantics, cost, transport, or failure mode.

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?

There is no output schema, so the description must convey what comes back; it explains that the grade and collision score derive from shift/collision counts but does not specify the grade scale or score format. Combined with the well-covered inputs, pricing, and 402 behavior, this is nearly complete for a pure-computation tool.

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?

Schema description coverage is 0%, so the description must compensate, and it does: it states that comparison happens by slot, offset, and size, and clarifies that 'a variable is one slice of a single slot', which gives meaning to the offset/size fields that the schema leaves undocumented. It never explicitly maps the previous/next arrays to before/after layouts, and says nothing about optional offset/size defaults, so it is good but not exhaustive.

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?

The description names a specific verb (compare) and resource (two caller-supplied storage layouts) and then defines the two key outcomes it computes: a 'shift' is a name that moves, a 'collision' is different names occupying the same bytes. That is enough for an agent to distinguish this purely computational grader from the chain-facing siblings such as proxy-upgrade-storage-audit.

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?

It makes the calling context clear by specifying 'caller-supplied' layouts and 'No chain is queried', which tells the agent to use this only when it already holds both layouts rather than looking them up. It does not explicitly name an alternative tool or state when not to use it, so it falls short of full routing guidance.

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