Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_notarize

Read-onlyIdempotent

M2M Cryptographic Timestamp and SHA-256 Proof-of-Existence signed with ECDSA secp256k1 (0.0050 USDC / 1 credit).

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": "grid402_notarize"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesText or JSON payload to hash (SHA-256) and timestamp cryptographically.
payment_tx_hashNoOptional txHash on Base Mainnet, Session Pass token (pass_g402_...), EIP-3009 base64 payload, or demo for Sandbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: the algorithms used and the cost (0.0050 USDC / 1 credit). It stops short of describing what the returned proof contains or how payment settlement affects the call.

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 front-loaded sentence names the mechanism, the algorithm, and the price with no filler. The dense parenthetical pricing is slightly awkward but earns its place by warning about a paid call.

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?

The tool is simple (two parameters), but with no output schema the description should say what the notarization returns — hash, timestamp, signature, proof identifier — so an agent can plan downstream use. It also omits any note on determinism or whether the same content yields the same proof, which matters given idempotentHint=true.

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%, and the schema itself explains both `content` and the accepted payment forms for `payment_tx_hash`. The description adds only the word 'cryptographically' and the price, so it neither needs to nor does compensate for any gap; baseline 3 applies.

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 concrete operation and artifact: a cryptographic timestamp plus SHA-256 proof-of-existence signed with ECDSA secp256k1. That is specific enough that an agent knows exactly what it produces. It does not, however, distinguish itself from likely siblings such as grid402_verify or grid402_crypto, leaving the agent to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of an alternative tool for checking or verifying an existing proof. The only contextual signals are the 'M2M' framing and the price, neither of which tells an agent when this tool is the right choice versus a sibling.

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.