Skip to main content
Glama
Bookipi MCP Server

Bookipi MCP Server

bookipi_open

Opens a Bookipi page in your signed-in Cloud Browser so you can manage invoices, customers, and proposals. Use it to start working with your Bookipi account data.

Instructions

Open a Bookipi page in your signed-in Cloud Browser (default https://web.bookipi.com) to work with manage invoices, customers and proposals.

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": "bookipi_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://web.bookipi.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It adds useful context that the page opens in a 'signed-in Cloud Browser' and gives the default URL, but it does not say whether an existing page is replaced, whether a new tab is opened, what permissions or session state are required, or how the call affects subsequent browser tools. This is partial behavioral disclosure for a simple navigation tool.

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?

The definition is a single front-loaded sentence with no redundant explanation. The only blemish is the awkward phrase 'to work with manage invoices,' which slightly reduces polish but does not obscure the main action.

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 one-parameter navigation tool with no output schema, the description covers the core action, default URL, and signed-in browser context. It is still incomplete about how the open operation relates to sibling tools such as bookipi_click, bookipi_read, and bookipi_type, and about what happens when a page is already open.

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%, and the sole 'url' parameter is already documented in the schema with its default. The description repeats the default URL and adds only the general concept of opening a Bookipi page, not which non-default URLs are valid or how the URL interacts with the signed-in browser context. Baseline 3 is appropriate when the schema already explains the parameter.

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?

The description states a clear verb and resource: 'Open a Bookipi page in your signed-in Cloud Browser.' It also names the business context (invoices, customers, proposals), which helps distinguish it from action-oriented siblings like bookipi_click, bookipi_read, and bookipi_type. However, it does not explicitly contrast itself with those siblings, so it is clear but not fully differentiated by wording.

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 by 'to work with manage invoices, customers and proposals' and by the need to open a page before interacting with it. But the description gives no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives such as using bookipi_status or bookipi_guide first. The guidance is adequate only by inference.

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