Skip to main content
Glama

domain_profile

Read-only

Get technology, DNS, mail security, TLS and hosting findings in one domain profile. 0.035 USDC per request.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name only, for example example.com; no URL, port or path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful non-schema context: a per-request price of 0.035 USDC, which matters for cost-aware planning. It says nothing about response latency, rate limits, or whether a failed or unknown domain still incurs the charge.

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?

Two short sentences with zero waste: the capability and its scope come first, and the pricing note follows. Nothing is buried or repeated.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing the return value; listing the finding categories helps, but it does not say how those findings are structured or what happens with partial data. Pricing and the single-parameter contract are covered, making it adequate but not complete for a tool with five finding sections.

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?

With one parameter and 100% schema description coverage, the schema fully documents the domain argument including the 'no URL, port or path' constraint. The description adds no further meaning about the parameter, so the 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 ('Get') and resource ('domain profile') and enumerates the finding categories returned: technology, DNS, mail security, TLS, hosting. That is enough for an agent to distinguish it from ip_reputation or speech_to_text, though it never names a sibling or says how it differs from technology_stack, which by name suggests overlapping coverage.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase 'in one domain profile' faintly implies this is a consolidated alternative to several single-purpose lookups, but the agent is left to infer that, and nothing tells it when a narrower sibling would be cheaper or more appropriate.

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