Skip to main content
Glama

Choose the cover photo

set_cover_photo

Puts a photo first in its group (the unit or the venue), so it is the one guests see in lists. 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>",
      "photo_id": "<photo_id>"
    },
    "name": "set_cover_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
photo_idYes
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose a non-read-only, non-destructive, non-idempotent mutation, so the safety profile is covered. The description usefully adds the guest-visible consequence and the auth requirement (address plus access key), but omits the key behavioral question for a reordering tool: whether the prior cover photo is demoted or cleared, and whether the call fails if the photo is not already in the group.

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?

Two short sentences, front-loaded with the effect and followed by the scope and credential requirement. The parenthetical clarifying 'group' is the only slightly noisy element.

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 three-parameter mutation with no output schema, the description covers what it does, which object it acts on, and what credentials are needed. The remaining gap, behavior of the displaced cover photo, is a genuine but secondary omission.

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 67%, with photo_id carrying no schema description at all. The description implies photo_id refers to a photo already in that venue's group via 'puts a photo first in its group', and reiterates the address/access_key scoping, but it never states whether the photo must already exist or what happens to the previous cover.

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 names a specific verb and effect: putting a photo first in its group so guests see it in lists, scoped to one venue. That distinguishes it from add_photo/remove_photo by outcome, though the parenthetical '(the unit or the venue)' leaves mild ambiguity about which group the photo is being ordered within.

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 stated goal (make a photo the one guests see in lists), so an agent can infer the intent. However, no explicit when-to-use conditions, prerequisites, or alternatives (e.g. add_photo first) are named.

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