Skip to main content
Glama

reject_invoice

Reject an invoice with a specified reason so it will not be paid; optionally add a note for the rejection record.

Instructions

Reject an invoice. It will not be paid.

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": {
      "invoice_id": "<invoice_id>",
      "reason": "<reason>"
    },
    "name": "reject_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
reasonYes
invoice_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the key effect (the invoice will not be paid), which is valuable, but says nothing about reversibility, whether the vendor is notified, or what permissions are required for a destructive mutation.

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 short sentences, front-loaded with the action and immediately followed by the outcome; no filler. It is arguably too terse for the gaps it leaves, but there is no wasted wording.

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?

For an irreversible-looking mutation tool with no annotations, no output schema, and zero parameter documentation, the definition should at minimum cover reversibility, notification side effects, and error behavior. None of that is present.

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 description coverage is 0% across three parameters. The description does not explain invoice_id format, when to pick each reason enum value, or how note is used, so it fails to compensate for the undocumented schema.

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?

"Reject an invoice" names a specific verb and resource, and the second sentence states the operational outcome ("It will not be paid"), which distinguishes it from the obvious sibling pay_invoice. It does not explicitly name a contrasting sibling, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no stated when-to-use guidance, no prerequisites (e.g., approval status or period-open state), and no named alternative such as pay_invoice or request_approval. The only usage signal is the implied consequence of non-payment.

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