Skip to main content
Glama

mocop

get_domain_discovery

Read-only

List everything indexed for a domain.

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

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile and closed-world scope are covered structurally. The description adds no behavioral detail beyond that: no indication of result size, pagination, ordering, or whether unknown domains yield an empty result versus an error — exactly the questions a "list everything" tool raises.

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

Conciseness4/5

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

A single short sentence with no filler and the key scope ("for a domain") placed up front. It earns its place as far as it goes; the problem is under-specification, not verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 carries full responsibility for telling the agent what comes back, and "everything indexed" does not do that. For a discovery/listing tool with one undocumented parameter and no return-value information, the definition leaves the agent guessing about both input format and response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the single required `domain` parameter is documented nowhere. The description's phrase "for a domain" only weakly signals that the parameter is a domain identifier; it says nothing about accepted format (bare name vs. URL vs. ID) or whether the domain must already be known/verified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a verb ("List") with a resource scope ("everything indexed for a domain"), so the general action is graspable. However, "everything indexed" is undefined — an agent cannot tell whether this returns DNS records, capabilities, entities, or a domain metadata summary — and nothing distinguishes it from siblings such as get_entity or domain_dns_guide.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives, no prerequisites, and no exclusions. An agent seeing get_entity, search_capabilities, and get_domain_discovery side by side has no textual basis for choosing this one; the only hint is the word "discovery" in the name, which is implicit at best.

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