Skip to main content
Glama

booker_read

Read the current Booker page to return its text and numbered buttons, links, and fields, with optional element-scoped reading.

Instructions

Read the current Booker page: its text and numbered buttons, links and fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "booker_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden and it partly meets it: "read" signals a non-mutating snapshot and the returned payload is described, which matters because there is no output schema. It does not state whether the page is re-fetched live or cached, whether the read has any size or cost limits, or that the numbering is regenerated each call, all of which affect safe repeated use.

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?

A single front-loaded sentence with the verb first and the return contents enumerated, with no filler. It is efficient, though the list of returned item types could be framed more usefully as the mechanism an agent acts on.

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?

The tool is simple: one optional parameter, no nested objects, no output schema, and no annotations. Within that scope the description covers purpose and return shape, which is the main gap a missing output schema creates; only the element-numbering linkage and refresh behavior remain unstated.

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?

Coverage is 100% for the single optional "element" integer, and the schema already says "Read only inside this element." The description adds nothing about the parameter, notably not the key linkage that element numbers refer to the numbering produced by this same read, so it neither compensates nor misleads.

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?

"Read the current Booker page" gives a specific verb and resource, and the colon clause names what comes back: text plus numbered buttons, links and fields. It is clear on its own, but it never contrasts itself with siblings such as booker_click or booker_type, leaving the agent to infer that this is the inspection step before an interaction step.

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 only implied: an agent can guess that it reads before it clicks or types, but the description gives no explicit when-to-use, no statement of what to do with the numbered elements afterward, and no exclusions. No alternative tool is named, and the omission is not alleviated elsewhere in the definition.

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