Veqen: AI cost monitoring and protection

An agent action

agent_action

action get (Veqen's answer as it stands, the approval and the matched transaction) or cancel (the agent didn't go through with it: it stops counting toward the month and a pending approval closes).

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": {
      "action_id": "<action_id>"
    },
    "name": "agent_action"
  }
}

Input Schema

Name	Required	Description	Default
`action`	No		get
`action_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond the annotations, the description adds meaningful consequences: cancel stops the action from counting toward the month and closes a pending approval, while get returns specific related records. It does not explain reversibility, error behavior, or permission requirements, but the annotations already cover the safety profile and the description adds non-obvious mutation effects.

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?

The description is a single front-loaded sentence contrasting the two actions, with no filler. The parenthetical structure is slightly dense but still efficient and readable.

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?

An output schema exists, so return-value details are not required, and the annotations cover safety hints. Still, the description leaves the required action_id parameter undocumented, which is a notable gap for a tool whose schema provides no parameter descriptions.

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 compensate. It explains the semantics of the action enum values (get vs cancel) beyond their names, but it completely omits any explanation of the required action_id parameter and its expected identifier format.

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 clearly defines the two operations on an agent action: get retrieves the current answer, approval, and matched transaction, while cancel aborts it. The resource is specific enough, though the title 'An agent action' is tautological and the description does not explicitly name the required action_id parameter.

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?

It gives an implied condition for cancel ('the agent didn't go through with it') and explains what get returns, which helps choose between the two modes. However, it does not state when to use this tool versus siblings like agent_approvals or record_agent_actions, nor does it mention exclusions or prerequisites.

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?