Skip to main content
Glama

Owner’s claim link

get_claim_link

A new link for the owner to claim this draft venue (the previous link stops working). The owner opens it, confirms with a code sent to their email and accepts the terms; then the booking pages open to customers. Until then the venue takes no members or bookings and sends no emails, and it is deleted automatically on its expiry date. 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_claim_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.1/5.0
Behavior5/5

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

Annotations only flag non-read-only, non-idempotent, non-destructive; the description adds substantial behavior: previous link invalidation, owner email-code/terms confirmation, customer pages opening only after acceptance, no bookings/emails before then, and auto-deletion on expiry. This is rich disclosure beyond annotations; the prior-link invalidation is a lifecycle consequence rather than a direct contradiction of destructiveHint=false.

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?

The purpose is front-loaded and the lifecycle details are relevant, with little filler. The final sentence largely restates required inputs already covered by the schema, and the semicolon-heavy flow is dense.

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 mutation with no output schema, the description covers the owner workflow, gating effects, and expiry deletion well enough to call it safely. It omits error/permission cases and does not clarify whether the link itself has a separate expiry.

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 coverage is 100% for address and access_key, and the description only restates that the tool acts on one venue via those values. It adds no format, validation, or alternative-parameter meaning beyond the schema.

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 description states a specific resource and action: generating a new owner claim link for a draft venue, and notes the prior link stops working. It does not explicitly name sibling alternatives such as get_venue, so it is clear but not fully differentiated by comparison.

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?

It gives clear context for use—when an owner needs to claim a draft venue—and explains the post-call workflow. It does not state when not to use it or name alternatives, so it lacks explicit 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