Veqen: AI cost monitoring and protection

One spike

get_spike

Read-onlyIdempotent

One spending spike, by the id list_anomalies gives: what it cost against a usual day, and the models, features, customers and users that moved most against the same weekday a week before.

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": {
      "spike_id": "<spike_id>"
    },
    "name": "get_spike"
  }
}

Input Schema

Name	Required	Description	Default
`spike_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive), and the description adds real context: what the numbers mean (cost against a usual day) and the comparison baseline (same weekday a week before). That baseline detail is genuinely useful for interpreting results and is not available anywhere in the structured fields.

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?

A single dense sentence with zero filler, front-loading the resource and the id provenance. The clause structure is slightly awkward ('by the id list_anomalies gives'), which costs a little readability but not correctness.

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 present, the description needn't enumerate return fields, and it instead explains the analytical meaning of the response and the comparison window. Combined with full annotation coverage and a single required parameter, an agent has what it needs to call this correctly; only edge cases (invalid or stale ids) are unaddressed.

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?

Schema description coverage is 0%, so the description must compensate, and it does by identifying the id's origin and namespace (the ids returned by list_anomalies). It doesn't state format or validation rules, but the schema already constrains the type to a positive integer.

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 precisely what is fetched: a single spending spike, identified by an id, along with cost-versus-usual-day and the top-moving models, features, customers and users. It also explicitly distinguishes itself from list_anomalies, the sibling that produces the ids, so an agent can route correctly without opening either schema.

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?

Gives an explicit prerequisite and alternative route: the id must come from list_anomalies, so the agent knows it should list first and then fetch detail. No explicit when-not guidance, but for a straightforward detail-fetch tool the routing condition is the one that matters and it is present.

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?