Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

Search LIGHTHOUSE

search
Read-onlyIdempotent

Search LIGHTHOUSE knowledge: pass a crypto address to get its freeze-risk record, or keywords (risk levels, how Tether freezes work, coverage, statistics, pricing, API/MCP access). Returns result ids for the fetch tool.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesAddress or keywords.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description nevertheless adds the important trait that this is a two-step tool returning only result ids rather than content, which determines how the agent must sequence calls. It omits result limits, ranking, and empty-result behavior, keeping it short of a 5.

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, front-loaded with the search scope, then the address mode, the keyword mode, and the return contract. Every clause carries information an agent needs; nothing is padding.

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?

With no output schema, the description correctly discloses that only result ids come back and that fetch completes the workflow. For a single-parameter read-only search that is close to complete, though it says nothing about result volume, ranking, or what a result id resolves to.

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% for the single query parameter, whose schema text already says 'Address or keywords.' The description enumerates example keyword categories, which adds modest interpretive value but largely restates the schema's dual-mode contract. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

States a specific verb+resource (search LIGHTHOUSE knowledge) and spells out the two input modes: a crypto address for a freeze-risk record, or keywords covering risk levels, freeze mechanics, coverage, statistics, pricing, and API/MCP access. It also names the downstream fetch tool, so an agent can tell it apart from the retrieval siblings without opening a 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?

Gives clear conditional guidance: use a crypto address for a specific freeze-risk record, use keywords for topical questions, and follow up with the fetch tool to get content. It does not explicitly exclude or compare against direct-check siblings like check_address, but the two-mode routing and the fetch handoff are concrete rather than implied.

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