Skip to main content
Glama
Sign In
billy-mcp

billy-mcp

by Cimalys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

billy_attach_file_to_bill

Link an uploaded file (e.g., receipt PDF) to a designated bill. Requires explicit confirmation (confirm:true) to commit changes.

Instructions

Attach an uploaded file (receipt PDF, etc.) to a bill. WRITE — requires confirm:true.

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": {
      "billId": "<billId>",
      "fileId": "<fileId>"
    },
    "name": "billy_attach_file_to_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
billIdYes
fileIdYes
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

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description effectively discloses that this is a mutation (WRITE) and that confirm=true is mandatory to execute. This gives essential behavioral context for safe invocation. Lacks details on failure modes or side effects.

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: one sentence plus a succinct note about confirm. No redundancy or filler. Front-loaded with action and resource.

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 three-parameter tool with no output schema, the description covers the core action adequately. However, it does not explain prerequisites (e.g., file must already be uploaded) or what happens on success (e.g., response, side effects), leaving minor gaps.

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

Parameters2/5

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

Schema coverage is only 33% (only confirm has a description). The description adds minimal meaning beyond parameter names for billId and fileId; it implies fileId refers to an uploaded file but provides no detail about expected formats or sources.

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 the action (attach), the target (bill), and the type of file (uploaded receipt PDF). It distinguishes from sibling tool billy_attach_file_to_invoice by specifying a different resource.

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?

The description notes that this is a WRITE operation requiring confirm:true, which guides invocation. However, no explicit when-to-use or when-not-to-use guidance is given, nor comparisons to alternative tools like billy_upload_file or billy_attach_file_to_invoice.

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