Skip to main content
Glama
Billdr MCP Server

Billdr MCP Server

billdr_open

Opens a Billdr page in your signed-in Cloud Browser so you can manage projects, quotes, change orders, invoices, budgets, timesheets, and daily logs.

Instructions

Open a Billdr page in your signed-in Cloud Browser (default https://app.billdr.co) to work with projects, quotes, change orders, invoices, budgets, timesheets and daily logs.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.billdr.co

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/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 usefully discloses that the browser session must be signed in and that the default target is https://app.billdr.co, but it does not say whether opening replaces the current page, waits for load, or returns anything about the opened page.

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?

The definition is a single front-loaded sentence with no waste: it leads with the action, parenthetically states the default, and then briefly scopes the kinds of Billdr content the page supports. The entity list is relevant context rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity tool with one optional, fully documented parameter and no output schema, the description gives enough information to invoke it correctly: action, environment, default URL, and page scope. The remaining gaps are mainly behavioral and routing details rather than missing invocation essentials.

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 single `url` parameter is already documented with its default in the schema. The description repeats the default URL but adds no additional format, syntax, or behavioral meaning for the parameter, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb/resource pair: 'Open a Billdr page' in the 'signed-in Cloud Browser'. It also gives the default URL and scopes the page type to projects, quotes, change orders, invoices, budgets, timesheets, and daily logs, which makes the navigation purpose clear without opening the schema.

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 context is implied by saying the tool is used 'to work with projects, quotes,' and related entities, but there is no explicit when-to-use, when-not-to-use, or alternative-tool routing. The signed-in browser requirement is stated, but the agent is left to infer when opening a page is preferable to other page interaction tools.

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