Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

Fetch LIGHTHOUSE record

fetch
Read-onlyIdempotent

Fetch the full text of a search result by id (address:, doc: or stats:overview).

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId from search results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 that the return is the full text (versus a snippet) and what id shapes are legal, but says nothing about size limits, missing-record behavior, or rate limits.

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 front-loaded sentence with the action first and the id-form enumeration in a compact parenthetical. No filler, nothing redundant with the schema.

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 one-parameter read tool with no output schema, saying it returns "full text" plus the accepted id formats is nearly enough. Minor gap: nothing about what happens when the id is unknown or the record does not exist.

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?

Schema coverage is 100% and there is only one parameter, so the baseline is 3; the description earns above that by documenting the id namespace prefixes (address:, doc:, stats:overview), which the schema's generic "Id from search results" does not.

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?

"Fetch the full text of a search result by id" gives a specific verb (fetch), resource (full text of a search result), and enumerates the id forms accepted (address:, doc:, stats:overview). It is clearly not the search tool itself, though it never names `search` explicitly as the producer of those ids.

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?

Usage is implied: you call this after obtaining an id from search results, and the id-prefix list hints at the three record families. There is no explicit when-not guidance or statement of which sibling to use for listing/searching instead.

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