Skip to main content
Glama

Mark booking seen

mark_booking_seen

Mark a booking as seen so it leaves the attention list.

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": {
      "booking_id": "<booking_id>"
    },
    "name": "mark_booking_seen"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_idYes
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds real value beyond them by disclosing the consequential effect — the booking is removed from the attention list — which the agent could not infer from the annotations. It leaves open whether the seen state is per-user or global and whether it can be undone, keeping it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single eleven-word sentence with no filler, and the effectful clause is placed immediately after the action so the agent reads the consequence first. Nothing is redundant or buried.

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?

For a simple two-parameter mutation with no output schema, the description covers the what and the outcome adequately. It omits the meaning of the 'seen' state (per-user vs. business-wide) and any note on return or idempotency, which would matter when the tool is called more than once.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: business_id is documented in the schema but booking_id carries only a uuid format. The description says nothing about which booking identifier is expected or how business_id relates to the booking, so it does not compensate for the coverage gap.

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 ('Mark ... as seen') and resource ('a booking') and states the observable outcome ('leaves the attention list'), which distinguishes it from siblings like get_attention_bookings or complete_booking. It stops short of naming a sibling explicitly, but the effect is unambiguous.

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: call this once a booking has been reviewed so it drops off the attention list. There is no explicit when-not guidance (e.g. when to use complete_booking or reject_booking instead of merely marking seen) and no prerequisites such as needing attention list access first.

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