Skip to main content
Glama
Bookibles MCP Server

Bookibles MCP Server

bookibles_type

Type text into a specified numbered field on the current Bookibles page, using the field number from the last read to target form inputs accurately.

Instructions

Type text into a numbered field 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>",
      "text": "<text>"
    },
    "name": "bookibles_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

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does not say whether existing field content is replaced or appended, whether the field must be focused first, what happens with an invalid element number, or what error behavior to expect — all material for a UI-mutating action.

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 tight sentence with the key scope (current page) placed where it is noticed. No filler, though it is short enough that a clause on replacement behavior could have been added cheaply.

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?

Low complexity (2 required params, no nested objects, no output schema) keeps the bar moderate, and the schema covers parameter meaning. Still, a stateful UI tool with zero annotation coverage should disclose what typing does to existing content and its preconditions.

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 100%, so both parameters are already documented, and "numbered field" lightly reinforces the meaning of element. Beyond that the description adds no format or validation detail over the schema.

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 specific verb ("type text") and target ("a numbered field on the current Bookibles page"), which clearly separates it from siblings like bookibles_click or bookibles_read. It stops short of naming an alternative or the precondition that a page must already be open.

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?

The phrase "on the current Bookibles page" implies state dependency and that a read must precede it (field numbers), but the description never states prerequisites explicitly nor says when to use this instead of click or read. Usage is only inferable, not spelled out.

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