Skip to main content
Glama
Bookipi MCP Server

Bookipi MCP Server

bookipi_guide

Call this first to learn Bookipi's screens and sign-in link for managing invoices, customers, and proposals.

Instructions

How to work in Bookipi (manage invoices, customers and proposals): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Bookipi, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read-only informational response ('its screens and the sign-in link'), but does not state whether it returns a URL, procedural text, or screen descriptions, nor whether sign-in requires credentials. The hint about content is useful but partial.

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?

Two compact sentences with the imperative 'Call this first' front-loaded and no filler. The parenthetical coverage list is slightly compressed to the point of being cryptic ('its screens and the sign-in link'), but nothing is wasted.

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 simple, single-optional-parameter guidance tool with no output schema, the description covers what it is and when to call it. It does not explain what the agent gets back or how the optional task string affects the answer, which leaves a meaningful gap for an orientation tool.

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 the schema already documents the single optional 'task' parameter, and baseline is 3. The description never mentions that a free-text goal can be supplied to tailor the guidance, which is the one place it could have added meaning beyond 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?

The description names the domain (Bookipi), the covered areas (invoices, customers, proposals), and the artifact (screens and the sign-in link), which distinguishes it from the action-oriented siblings like bookipi_click and bookipi_type. It lacks a crisp verb ('how to work in' is a resource framing rather than an action), but the intent 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this first' gives an explicit ordering rule relative to the other Bookipi tools, which is the key usage decision for this tool. There are no when-not conditions or named alternatives, but for a guide tool the primary guidance is sequencing, and that is stated directly.

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