Skip to main content
Glama

booker_type

Types text into a specified numbered field on the current Booker page, enabling automated form entry during appointment, client, or sales workflows.

Instructions

Type text into a numbered field on the current Booker page.

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": {
      "element": "<element>",
      "text": "<text>"
    },
    "name": "booker_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It does not say whether typing replaces or appends to existing field content, whether it submits the form, what happens with an out-of-range field number, or whether focus is required.

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 front-loaded sentence with the action and target stated immediately and no filler. It is appropriately sized for the surface-level claim it makes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an unannotated mutating tool with no output schema, the definition is incomplete: it omits session prerequisites, replacement-versus-append behavior, and error conditions. Enough is present to guess the call shape, but not enough to invoke it safely in ambiguous states.

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%, and the schema already explains both 'text' and 'element' (including 'Field number from the last read'). The description's phrase 'numbered field' merely echoes the schema without adding format, ordering, or edge-case detail.

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?

States a concrete action (type text) against a concrete target (a numbered field on the current Booker page), which is clearly distinct from sibling actions like click, close, open, or read. It stops short of naming those siblings, so differentiation is implicit rather than explicit.

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

Usage Guidelines2/5

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

No guidance on when to use this versus booker_click or booker_read, and no stated prerequisite that a page must already be open or that the field number must come from a prior read. The phrase 'current Booker page' hints at a session requirement but never states it.

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