Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_ssl

Read-onlyIdempotent

Inspect port 443 TLS/SSL certificate validity, issuer, SANs and expiration (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": {
      "host": "<host>"
    },
    "name": "grid402_ssl"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesTarget hostname to inspect on port 443 (e.g. base.org).
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context the annotations lack: the cost of 0.0050 USDC / 1 credit. It says nothing, however, about rate limits, failure modes for unreachable hosts or invalid chains, or how payment gating 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the inspected fields front-loaded and the price appended last. No redundant restatement of the tool name and no filler.

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?

For a simple two-parameter, read-only tool with full schema coverage, this is nearly complete, and with no output schema it usefully previews the returned fields (validity, issuer, SANs, expiration). The residual gap is that the paid-call flow and any error semantics for invalid or unreachable certificates are left unstated.

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 both 'host' and 'payment_tx_hash' are already documented in the schema, and the baseline of 3 applies. The description adds only an implicit constraint that the target port is fixed at 443, which is mildly useful but not 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?

The description gives a specific verb ('Inspect') and a precisely bounded resource ('port 443 TLS/SSL certificate'), then enumerates the exact fields surfaced: validity, issuer, SANs and expiration. That clearly separates it from data-lookup siblings like grid402_dns or grid402_domain_audit, though it never names an alternative explicitly.

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 explicit when-to-use or when-not-to-use guidance, and no prerequisites or exclusions are stated. An agent must infer from the field list that this is the tool for certificate-level questions, with no rule for choosing it over the neighboring domain/DNS tools.

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.