Skip to main content
Glama
benswel

QR for Agent

by benswel
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

get_custom_domain

Retrieve your custom domain configuration and DNS verification status for QR codes, including setup instructions to complete the process.

Instructions

Get your current custom domain configuration and DNS verification status. Returns the domain, whether DNS is active or pending, and setup instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • packages/mcp/src/tools.ts:815-822 (handler)
    The handler implementation for get_custom_domain, which makes a GET request to the /api/domain endpoint.
    get_custom_domain: {
  description:
    "Get your current custom domain configuration and DNS verification status. Returns the domain, whether DNS is active or pending, and setup instructions.",
  inputSchema: z.object({}),
  handler: async () => {
    return apiRequest("/api/domain");
  },
},

Tool Definition Quality

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the return structure (domain, DNS status, setup instructions) but omits explicit read-only/safety declarations, rate limits, or auth requirements that would help an agent understand operational constraints.

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 efficient sentences with zero waste. First sentence establishes the action and scope, second details the return payload. Information is front-loaded appropriately.

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?

Despite lacking an output schema, the description adequately documents the return values (domain, DNS status, instructions). It is complete enough for a zero-parameter read operation, though explicitly contrasting with 'set_custom_domain' would have strengthened contextual understanding.

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?

The input schema has 0 parameters, which warrants the baseline score of 4. The description correctly requires no parameter explanation, though it could have noted 'no parameters required' for absolute clarity.

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 uses specific verb 'Get' with clear resource 'custom domain configuration' and aspect 'DNS verification status'. It also clarifies the return values (domain, status, instructions), distinguishing it from sibling 'set_custom_domain' as the read operation.

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

Usage Guidelines3/5

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

Usage is implied by the clear naming and 'Get' verb, but there are no explicit guidelines on when to use this vs 'set_custom_domain', nor prerequisites like requiring an existing domain configuration. No 'when-not-to-use' guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/benswel/qr-agent-core'

If you have feedback or need assistance with the MCP directory API, please join our Discord server