Veqen: AI cost monitoring and protection

Add a monthly bill

add_bill

Records a provider's monthly invoice total (period YYYY-MM), for providers whose billing Veqen can't read. Month-end books it. Needs an owner, admin or finance member.

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": {
      "provider": "<provider>",
      "period": "<period>",
      "amount": "<amount>"
    },
    "name": "add_bill"
  }
}

Input Schema

Name	Required	Default
`note`	No
`amount`	Yes
`period`	Yes
`currency`	No	USD
`provider`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare a non-readonly, non-idempotent, non-destructive write; the description adds genuinely new context by naming the required role (owner, admin or finance member) and the month-end booking side effect. It does not say what happens when a record already exists for the same provider+period — relevant given idempotentHint=false.

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?

Three short sentences, front-loaded with the core action and scope. 'Month-end books it' is terse to the point of being slightly cryptic, but no sentence is wasted.

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 mutating, non-idempotent tool with a full output schema and 0% schema coverage, the description covers the essentials (what, who can call it, downstream effect) but leaves duplicate handling, currency and note behavior unexplained.

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% across 5 parameters, so the description must compensate; it clarifies that amount is the invoice total and that period is YYYY-MM. It says nothing about currency (default USD, ISO-3 pattern) or note, leaving two parameters undocumented anywhere.

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?

States a specific verb (records) and resource (a provider's monthly invoice total) plus the key scoping condition: manual entry for providers whose billing Veqen can't read. That condition alone differentiates it from list_bills and the automated ingestion path.

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 makes the triggering condition clear ('providers whose billing Veqen can't read') and notes the downstream relationship ('Month-end books it'), implying this is the manual fallback before closing the month. It stops short of naming an explicit alternative tool or stating when not to use it.

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

All Veqen: AI cost monitoring and protection tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?