Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Keccak256, function selector: Keccak-256 hash, 4-byte selector and event topic

keccak
Read-only

Keccak-256 hash (the Ethereum hash) of text or of 0x hex bytes, as used for function selectors, event topics and storage slots. Use when building or decoding EVM calls. Example: text=transfer(address,uint256). Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "text": "<text>"
    },
    "name": "keccak"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText, or 0x-prefixed hex bytes, up to 10,000 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and idempotentHint=false. The description adds meaningful context beyond that: pricing ($0.01/call), first 25 free, failed calls free, and the fact that repeats are charged, which explains the non-free repeat behavior. It does not specify the exact return shape, but the billing and side-effect transparency is strong.

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 front-loaded with the core purpose, followed by a compact usage example and billing notes. It is dense but avoids filler; separating the return-format detail would improve structure, but every current sentence carries relevant information.

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 simple one-parameter tool with no output schema, the description covers input format, use case, pricing, and side-effect profile. The main gap is that it does not state what the call returns—whether a 32-byte hash, a 4-byte selector, or both—despite the title mentioning function selectors. That omission matters for an agent trying to use the result correctly.

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 coverage is 100%, and the schema already documents that 'text' can be text or 0x-prefixed hex bytes up to 10,000 characters. The description largely repeats that format, though the example 'text=transfer(address,uint256)' adds a useful concrete case. Baseline 3 is appropriate when the schema carries the parameter detail.

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 states a specific verb and resource—'Keccak-256 hash' of text or 0x hex bytes—and names concrete uses: function selectors, event topics, and storage slots. It also gives an example input, making the tool's purpose immediately clear 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a positive trigger, 'Use when building or decoding EVM calls,' plus a concrete example. However, it does not state explicit when-not conditions or name alternative tools, so the guidance is clear but not exhaustive.

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.