Skip to main content
Glama
Sign In

Supplier Invoice Tool

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Put an invoice on a job

assign_job_reference
Idempotent

Put an invoice (or some of its lines) on a job, when the supplier left the reference off or it was wrong.

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>",
      "job_reference": "<job_reference>"
    },
    "name": "assign_job_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoice_idYes
line_numbersNo
job_referenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent, closed-world write, so the safety profile is covered. The description adds the corrective-use context, but says nothing about whether an existing reference is overwritten, whether the supplier is notified, or what happens to lines not in line_numbers. That is a moderate gap for a mutation tool, not a contradiction.

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?

One sentence, front-loaded with the action and immediately followed by the qualifying condition. Nothing is wasted and nothing would be lost by trimming further.

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 3-parameter mutation with annotations but no output schema, the description covers the main case adequately but leaves the important edge cases open: line_numbers semantics, overwrite behavior, and what success returns. An agent could call it correctly for the happy path only.

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?

Schema description coverage is 0%, so the description must carry weight. It does map loosely onto all three params (invoice, some of its lines, job reference), but gives no format for job_reference and no basis for line_numbers (1-indexed? invoice line IDs vs. positions? whether omitting it means all lines). Meaning is implied, not specified.

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 gives a specific verb and resource ("Put an invoice ... on a job") and scopes it to whole invoices or a subset of lines via the parenthetical. It doesn't name or contrast with any sibling tool, so an agent must infer the boundary from names like review_invoice or push_bills_to_xero.

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?

It clearly states the triggering condition: when the supplier omitted the job reference or supplied a wrong one. That is genuine when-to-use context, but there are no exclusions (e.g. what to do if the invoice is already on a different job) and no named alternatives.

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

All Supplier Invoice Tool toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources