Skip to main content
Glama
Bookipi MCP Server

Bookipi MCP Server

bookipi_type

Types text into a chosen numbered field on the current Bookipi page by referencing the field number from the last read.

Instructions

Type text into a numbered field on the current Bookipi 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": "bookipi_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.3/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 it discloses almost nothing: whether typing replaces or appends to existing content, whether the field must be focused or the page open first, whether the action submits the form, and what happens on an invalid element number are all unstated.

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 verb first and zero wasted wording; nothing is padded or repeated. Brevity is appropriate here rather than verbose.

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 two-parameter tool with no output schema, the definition is minimally viable but leaves the agent guessing about mutation semantics (replace vs append) and prerequisite page state. An agent can call it, but not always correctly on the first try.

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%, with both parameters documented ('Text to type.' and 'Field number from the last read.'), so the baseline is 3. The description adds only the locational qualifier 'current Bookipi page' and no further semantics about the element indexing or text handling.

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 and target: 'Type text into a numbered field on the current Bookipi page.' That distinguishes it from siblings like bookipi_click or bookipi_read, though it doesn't name any sibling explicitly to reinforce the contrast.

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 rather than stated: 'on the current Bookipi page' and the schema's 'Field number from the last read' hint that a prior read and open page are prerequisites. There is no explicit when-to-use versus bookipi_click or bookipi_open, and no statement of what to do if the field number is stale.

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