Skip to main content
Glama
Bookibles MCP Server

Bookibles MCP Server

bookibles_click

Clicks a numbered element on the current Bookibles page, letting agents select page controls identified by a prior read.

Instructions

Click a numbered element on the current Bookibles 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>"
    },
    "name": "bookibles_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description bears the full disclosure burden. It does add the useful scoping fact that the target lives on the 'current' page, implying page state matters, but it never says whether clicking navigates, mutates state, waits for load, or what happens if the element number is stale or invalid.

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?

One short, front-loaded sentence with no filler. It is efficient, though the brevity verges on under-specification given the interactivity of the operation.

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?

This is a browser-interaction tool with no annotations and no output schema, so an agent gets no signal about post-click page state, waiting behavior, or error modes for invalid element numbers. For an action tool that changes UI state, the definition leaves too much to inference.

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?

Single required parameter at 100% schema description coverage, which already explains that 'element' is the element number from the last read. The description adds no format, range, or failure semantics beyond that, so the baseline of 3 applies.

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 verb (click) and target (numbered element on the current Bookibles page), which is clearly distinct from sibling verbs like read, type, open, and close. It stops short of explaining what clicking accomplishes, but the action itself 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 only implied: the phrase 'the current Bookibles page' hints that a page must already be loaded, and the schema note that the number comes 'from the last read' hints at a read-then-click workflow. Neither the prerequisite read step nor any when-not-to-use condition is stated in the description.

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