Veqen: AI cost monitoring and protection

Price a provider from its bill

price_from_bill

Sets a price per million tokens for that provider's models from a whole month's bill (bill_id from list_bills) and what they served.

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": {
      "bill_id": "<bill_id>"
    },
    "name": "price_from_bill"
  }
}

Input Schema

Name	Required	Description	Default
`bill_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations declare the write operation (readOnlyHint=false, non-idempotent, non-destructive). The description adds that it sets a price per million tokens for the provider's models based on a bill, but does not disclose effects on existing prices, reversibility, or permissions.

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 core action, no wasted words. The parenthetical for bill_id is efficient and informative.

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

Completeness4/5

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

With an output schema and annotations covering safety profile, the description adequately covers what the tool does and where the parameter comes from. It could further clarify side effects (e.g., overwriting existing prices), but it is sufficient for an agent to invoke correctly.

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

Parameters4/5

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

Only one parameter (bill_id) with 0% schema description coverage. The description compensates by explicitly naming its source (list_bills) and implying it refers to a whole month's bill, adding meaningful context beyond the 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?

States a specific verb (sets a price), resource (per million tokens for provider's models), and source (whole month's bill). It clearly distinguishes from set_price by deriving pricing from a bill, though it does not explicitly name the sibling.

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?

Provides context for when to use it: from a whole month's bill with bill_id from list_bills. However, it does not state when not to use it or compare to alternatives like set_price or get_model_price.

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?