Skip to main content
Glama

What Prove It Onchain offers

products
Read-onlyIdempotent

Use first if you are not sure which tool you need. Free, read-only. Lists both Prove It Onchain products and which tools belong to each: (1) Bitcoin vanity names with a signed agent profile ($21 + network fee), proofs ($1 + network fee) and free identity checks; (2) TOKENLOCK, zero-trust access for the token era: token-gate a site, API or members area to holders of a Bitcoin token or name, or sign in to a gated site with your own name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "products"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuinely new context: the call is free, requires no payment, and the content enumerates the two product lines with their price points, telling the agent what to expect before paying for anything else.

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 routing instruction and the free/read-only note are front-loaded, which is exactly right. The trailing product enumeration with inline pricing ($21, $1, network fees) is longer than strictly necessary for a catalog tool, though it does help the agent recognize product scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no input parameters and no output schema, the description carries the burden of describing what comes back, and it does: the product list and the tool-to-product mapping. Nothing needed to invoke it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. No misleading parameter language is present.

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 uses a specific verb and resource ("Lists both Prove It Onchain products and which tools belong to each") and explicitly positions itself as a discovery/routing entry point distinct from the operational siblings like buy_name or verify. An agent can tell immediately that this tool returns a catalog, not an action.

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?

"Use first if you are not sure which tool you need" gives clear when-to-use guidance, and "Free, read-only" removes any cost/risk hesitation. It implies skipping this when the agent already knows the target tool, but never states an explicit exclusion or names a follow-up alternative.

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