Skip to main content
Glama

Domain Redirects

domain-redirects
Read-onlyIdempotent

Use when the user asks where a domain redirects, whether domains are aliases, or to detect brand consolidations. Single-domain lookup.

Returns known redirects from or to the given domain.

Input parameters (filters): domain, match. Definitions in input schema.

Available output fields for the 'fields' parameter: source_domain, source_fqdn, linked_domain, linked_fqdn, record_date. Field details: https://docs.discolike.com.

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": {
      "filters": "<filters>"
    },
    "name": "domain-redirects"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOutput fields to include in response
formatNoResponse format: rows or columnarrows
contextNoWhy you are calling this tool, in a few words. No names or emails.
filtersYesRequest filters for domain redirect lookup.
llm_modelNoYour model id, or "unknown".
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
countNo
redirectsNo
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
      +  "_mcp_instructions": {
      +    "description": "Server-issued metadata for this conversation.",
      +    "properties": {
      +      "conversation_id": {
      +        "description": "The server-issued conversation identifier.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "count": {
      +    "type": "integer"
      +  },
      +  "redirects": {
      +    "anyOf": [
      +      {
      +        "items": {
      +          "properties": {
      +            "linked_domain": {
      +              "type": "string"
      +            },
      +            "linked_fqdn": {
      +              "type": "string"
      +            },
      +            "record_date": {
      +              "type": "string"
      +            },
      +            "source_domain": {
      +              "type": "string"
      +            },
      +            "source_fqdn": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      {
      +        "additionalProperties": {
      +          "items": {},
      +          "type": "array"
      +        },
      +        "required": [],
      +        "type": "object"
      +      }
      +    ]
      +  }
      +}
    • addedOutput schema / required
      Added value: +[]
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Why you are calling this tool, in a few words. No names or emails.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Your model id, or \"unknown\".",
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that results come from either direction ('from or to the given domain'), but that directionality is also expressed by the schema's match enum, so little genuinely new behavior is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The use-case lead is front-loaded and useful, but the enumerated output fields plus a docs URL duplicate information already available via the output schema and the fields parameter, adding bulk without new meaning.

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 annotations, a full-coverage schema, and a declared output schema, the description supplies the remaining piece – the user intents that should trigger the call and the bidirectional nature of results. It is essentially complete, only lacking explicit sibling routing.

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%, so both domain and match are fully documented in the schema. The description only names the filter parameters and defers ('Definitions in input schema'), which is explicit but adds no syntax or semantics beyond the structured data – 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?

States a specific verb+resource (domain redirect lookup) and frames the user intents it answers: where a domain redirects, whether domains are aliases, brand consolidations. 'Single-domain lookup' implicitly separates it from bulk-style siblings, but no sibling is named explicitly.

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 when-to-use cues tied to user phrasing ('asks where a domain redirects, whether domains are aliases'). No when-not-to-use conditions or explicit alternative tool names are provided, so it stops short of full routing guidance.

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