Skip to main content
Glama

Hall of Fame

get_hall_of_fame
Read-onlyIdempotent

Fetch the IntoDNS Hall of Fame to list top-scoring public domains or check domain membership. Use it to find examples of strong DNS/email posture or verify inclusion.

Instructions

Read-only fetch of the IntoDNS.ai Hall of Fame for top-scoring public domains. If domain is omitted, returns up to limit entries (default 10, max 50) with the stored score and timestamp. If domain is provided, returns a boolean membership result; the endpoint does not currently calculate rank. Use to show examples of strong DNS/email posture or check membership; use scan_domain for current evidence because Hall of Fame data may be older. No auth or destructive actions.

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": "get_hall_of_fame"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries
domainNoOptional domain to check for Hall of Fame presence

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain / maxLength
      Added value: +253
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description reinforces safety while adding genuinely new behavior: default 10 / max 50, the boolean-membership mode, and a disclosed endpoint limitation ('does not currently calculate rank'). It stops short of describing ordering or pagination of the list, which would complete the behavioral picture.

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?

Four sentences, front-loaded with what the tool is, then the two modes, then the alternative. No filler or restatement of the name; every clause carries information an agent would otherwise have to infer.

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?

No output schema exists, so the description must carry the return contract and does: a list of entries with stored score and timestamp, or a boolean membership result. Combined with the staleness caveat and the rank limitation, an agent has everything needed to call and interpret this tool.

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 already documents both parameters, so the baseline is 3; the description earns above that by explaining the consequence of supplying `domain` (switches to a boolean membership result) and restating the default/max for `limit`. It does not specify what `limit` does when `domain` is set (presumably ignored), a small ambiguity.

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?

Specific verb+resource (read-only fetch of the IntoDNS.ai Hall of Fame) with the scope spelled out: top-scoring public domains. It also distinguishes its two modes (list vs. membership check) and names the sibling scan_domain as the contrasting tool, so an agent can separate it from the other ~40 DNS tools 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 Guidelines5/5

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

States both use cases (show examples of strong DNS/email posture, or check membership) and explicitly routes the agent to scan_domain when current evidence is needed, with the reason given (Hall of Fame data may be older). It also states no auth is required, removing a common precondition question.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.