Veqen: AI cost monitoring and protection

List provider keys

list_provider_keys

Read-onlyIdempotent

Every key Veqen sees at the organization's AI providers, with its owner, status and the flags that make it risky (unused for 30 days, its owner left, open to any API). Needs an owner, admin, finance or security member.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_provider_keys"
  }
}

Input Schema

Name	Required	Description	Default
`offset`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description is not carrying the full safety burden. It adds useful context by naming the permission requirement and defining the specific risk flags returned, though it does not mention pagination or rate-limit behavior.

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 front-loaded with the core resource and scope, then adds the risk-flag parenthetical and access requirement. It is efficient and every sentence adds information, though the permission sentence could be packaged slightly more tightly.

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?

Because an output schema exists, the description does not need to explain return values, yet it still adds value by naming the owner, status, and risk flags. The main omission is pagination behavior for the offset parameter, which an agent would need to page through keys reliably.

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

Parameters2/5

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

The schema has 0% description coverage for the single offset parameter, and the description does not mention offset, pagination, or what the offset is relative to. The parameter is standard, but the description fails to compensate for the missing schema documentation.

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 states the resource and scope: every provider key the organization's AI providers expose to Veqen, including owner, status, and risk flags. It does not explicitly differentiate itself from sibling list tools such as list_members or list_models, but the purpose is understandable without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is an access prerequisite: the caller needs an owner, admin, finance, or security member. There is no stated when-to-use condition, no exclusion, and no comparison to alternative tools, so an agent gets no routing help beyond the permission note.

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?