Skip to main content
Glama
RoscoNL

intodns-mcp

by RoscoNL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_hall_of_fame

Read-onlyIdempotent

Fetch top-scoring public domains from IntoDNS.ai's Hall of Fame, returning entries with score and timestamp. Optionally check membership for a specific domain, returning a boolean result.

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.

Input Schema

TableJSON 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 readOnlyHint and destructiveHint, and the description adds value by noting the endpoint does not calculate rank, data may be stale, and no auth is required. These go beyond structured annotations to disclose useful limitations.

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?

Three concise, information-dense sentences with no redundancy. It front-loads the core purpose, then details modes and usage guidance, earning every word.

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?

Given no output schema, the description adequately explains the two possible outcomes (list with score/timestamp or boolean membership) and notes the rank limitation. It covers all relevant aspects for a simple read-only tool with two optional parameters.

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 covers both parameters, but the description adds meaning beyond schema by explaining conditional behavior (if domain omitted vs. provided), including the return type change and default/max limits, which is not fully expressed in the schema alone.

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 clearly states the tool fetches the IntoDNS.ai Hall of Fame, with specific verbs and resources. It distinguishes between two modes (list vs. membership check) and explicitly contrasts with scan_domain, making sibling differentiation clear.

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?

Provides explicit when-to-use guidance and names an alternative tool (scan_domain) for current evidence, noting that Hall of Fame data may be older. This gives clear context on appropriate use.

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

Deploy Server

Other Tools