Skip to main content
Glama
Billdr MCP Server

Billdr MCP Server

billdr_guide

Explains how to navigate Billdr projects, quotes, change orders, invoices, budgets, timesheets, and daily logs, including key screens and sign-in links; call this before other Billdr actions.

Instructions

How to work in Billdr (projects, quotes, change orders, invoices, budgets, timesheets and daily logs): 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": "billdr_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Billdr, 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?

No annotations are supplied, so the description carries the full disclosure burden. It implies a non-mutating reference/help call and adds the useful sequencing behavior, but it does not state whether invoking it performs any action, what comes back, or how large the response is.

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 scope list and the "call this first" directive front-loaded; nothing is redundant. The parenthetical domain list is long but earns its place by helping the agent match a user task to this tool.

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 single free-text-parameter tool with no output schema, the description should at least characterize the returned guidance. It covers scope and sequencing well but leaves the return value unstated, which is the main remaining gap.

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?

The single parameter has 100% schema description coverage ("What you want done in Billdr, in your words"), so the schema already explains it. The description does not restate or enrich the parameter semantics, which is the baseline 3 case for high coverage.

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 identifies the tool as a guide to working in Billdr and enumerates the covered domains (projects, quotes, change orders, invoices, budgets, timesheets, daily logs) plus screens and the sign-in link. That is enough for an agent to distinguish it from action siblings like billdr_click or billdr_open, though it never states the output form (guidance text versus an action).

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" is explicit sequencing guidance that tells the agent to consult this tool before the action-oriented siblings. There is no statement of when not to use it or of conditions where a sibling should be preferred, so it falls short of a full when/when-not treatment.

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