Skip to main content
Glama

Use the venue’s own domain

get_dns_instructions
Read-onlyIdempotent

How the venue can use its own address (e.g. book.yourgym.com) for its booking pages. Available on the Pro plan; the owner switches it on in Settings → Link and domain after adding the DNS record. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>"
    },
    "name": "get_dns_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoOptional, e.g. book.yourgym.com.
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so safety is covered; the description adds real value beyond them by disclosing plan gating (Pro), that activation is a manual owner action rather than something this call performs, and that it is scoped to a single venue. It doesn't describe the shape of the returned instructions (e.g. record type/host/value), which keeps it from a 5.

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?

Three tight sentences with the core meaning front-loaded and the plan/setup caveats after it. Nothing is redundant, though the final sentence largely restates the schema's required fields.

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?

For a simple read-only lookup with only three well-documented parameters and no output schema, the description supplies the relevant prerequisites and scope. The only gap is that it never hints at what the returned instructions contain, which would matter since no output schema exists.

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 the baseline is 3. The description reinforces that address and access_key identify exactly one venue, but it adds no syntax or format detail beyond the schema and says nothing extra about the optional domain parameter.

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?

The first sentence states a specific resource and outcome: instructions for how a venue can use its own address (e.g. book.yourgym.com) for booking pages. That is more than a restatement of the name, and an agent can tell it apart from setup-guide siblings like get_embed_code or get_claim_link by the custom-domain framing. It stops short of explicitly naming a sibling alternative, so not a 5.

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?

Useful context is given: the feature requires the Pro plan and the owner must switch it on in Settings → Link and domain after adding the DNS record. That tells the agent roughly when this applies, but there is no explicit when-to-use/when-not-to-use guidance and no routing to alternatives for other setup tasks.

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