Skip to main content
Glama

Check wallet site

check_wallet_site
Read-onlyIdempotent

Check whether a web address is an official Ledger or Coinbase site (address check only).

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": {
      "url": "<url>"
    },
    "name": "check_wallet_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWeb address or hostname, e.g. https://shop.ledger.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile needs no restating. The description adds real behavioral context beyond them: the check covers the address only, not site content or certificates, which tells the agent how much trust to place in a positive result.

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?

One sentence, no filler, with the scope qualifier placed at the end where it qualifies the whole claim. Nothing to trim.

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 single-parameter read tool, the definition is nearly sufficient, but with no output schema the description never indicates what a result looks like (boolean, verdict, matched brand), leaving the agent to guess at the response shape.

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?

There is a single parameter with 100% schema description coverage, including an example URL, so the schema carries the burden. The description adds nothing about accepted formats (bare hostname vs. full URL, trailing paths) beyond what the schema already shows, so 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?

Specific verb ('Check') plus resource ('a web address') and an explicit criterion ('official Ledger or Coinbase site'), so the agent knows exactly what the tool determines. The sibling tools are all deal-related, so no differentiation statement is needed; the scope parenthetical further narrows the meaning.

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

Usage Guidelines3/5

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

The purpose implies when to reach for it (verifying a site is legitimate), and '(address check only)' hints at a limitation. But there is no explicit statement of when to use it versus other approaches, no prerequisites, and no guidance on what to do with a negative result.

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