Skip to main content
Glama
Sign In
billy-mcp

billy-mcp

by Cimalys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

billy_create_bill

Create a bill in Billy accounting by providing contact, date, currency, and line items. Requires explicit confirmation to execute.

Instructions

Create a new bill. WRITE — requires confirm:true. Shape: { contactId, entryDate, currencyId, lines: [{ accountId, description, amount, taxRateId? }] }

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": {
      "bill": "<bill>"
    },
    "name": "billy_create_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYes
confirmNoREQUIRED to execute. Pass true to actually run the mutation. Without it, this tool returns a dry-run preview of what would happen — explicit second call with confirm:true is needed to write.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided; the description discloses the WRITE operation, confirm requirement, and dry-run preview. It adds key behavioral context but omits details like permissions or error handling.

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?

Extremely concise with no wasted words. Purpose and key usage information are front-loaded in two short sentences.

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?

Covers the critical confirm behavior and bill shape, but lacks details on return values, validation rules, or required nested fields. Adequate for a create tool with moderate complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers confirm with description; bill object is freeform. The description adds a specific shape (contactId, entryDate, currencyId, lines) that goes beyond the schema, aiding parameter understanding.

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 clearly states 'Create a new bill.' and provides a specific shape, distinguishing it from siblings like billy_update_bill and billy_delete_bill.

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?

Explicitly notes the two-step confirm process ('WRITE — requires confirm:true') and dry-run behavior, but doesn't explicitly contrast with other create tools or mention alternative contexts.

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

Deploy Server

Other Tools