AutoFYI MCP

Overview Schema Source Related Servers Discussions Admin

prepare_direct_invoice

Read-only

Prepare a direct invoice for client jobs without interim billing, automatically blocking duplicate invoices for repeat clients unless overridden.

Instructions

Prepare a no-interim direct invoice. Repeating clients are blocked unless the duplicate-billing override is explicit.

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": {
      "client_id": "<client_id>",
      "jobs": "<jobs>"
    },
    "name": "prepare_direct_invoice"
  }
}

Input Schema

Name	Required	Default
`jobs`	Yes
`theme`	No	Standard
`client_id`	Yes
`invoice_type`	No	Final
`invoice_amount`	No
`approve_invoice`	No
`allow_repeating_client`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 3, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds a behavioral rule about blocking repeating clients without override, which is useful. However, it does not disclose what 'prepare' actually returns or what happens on successful preparation, so value beyond annotations is moderate.

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 description is two sentences, front-loaded with the core purpose, and every word adds value. No redundancy or filler.

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

Completeness2/5

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

With 7 parameters, no output schema, and no parameter descriptions in the schema, the description is far too sparse. It does not explain the jobs array structure, what 'prepare' returns, or how to provide the override parameter. The tool cannot be correctly invoked based on this description alone.

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?

The schema has 7 parameters with 0% description coverage, so the description must compensate. It partially does by implying invoice_type='Final' via 'no-interim' and by referencing allow_repeating_client via 'duplicate-billing override'. But it fails to explain jobs, amount, theme, approve_invoice, or client_id, leaving most parameters ambiguous.

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 'Prepare a no-interim direct invoice' with a specific verb and resource. The 'no-interim' qualifier distinguishes it from sibling tool prepare_interim_split, making the purpose 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?

The description gives clear context for use: direct invoices only, not interim. It also explicitly states a usage rule for repeating clients: they are blocked unless the duplicate-billing override is explicit. However, it does not name alternative tools or explicitly state when not to use it beyond the repeating-client block.

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

Deploy Server