Skip to main content
Glama

Gateway usage

vault_usage
Read-onlyIdempotent

Read metadata-only API-key gateway usage for this connector.

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": "vault_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that results are metadata only, so no key material or payload content is returned. It says nothing about pagination behavior or result shape, which the annotations cannot cover.

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 front-loaded sentence with no filler, and the key scoping constraint ('metadata-only') appears before the resource noun. Brevity here comes at the cost of substance rather than from trimming redundancy, but structurally it is clean.

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?

The tool is simple (one optional bounded parameter, no output schema), so the bar is low, but with no output schema the description is the only place that could say what a 'usage' record contains or how limit affects results. Those gaps matter for an agent deciding whether the response answers its question.

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?

Schema description coverage is 0% and the single 'limit' parameter is never mentioned in the description. Default 100 and max 500 are visible in the schema, but nothing tells the agent whether limit caps records, time buckets, or aggregation rows, nor whether results are truncated silently.

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 supplies a specific verb and resource: 'Read ... API-key gateway usage for this connector.' The qualifier 'metadata-only' scopes what is returned, and 'gateway usage' is distinguishable from sibling operations like vault_execute or vault_invoke_read. It stops short of naming what metrics 'usage' contains, so it is clear but not fully sharp.

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?

There is no when-to-use or when-not-to-use guidance and no mention of an alternative sibling. An agent must infer that this is the tool for inspecting quota/traffic stats as opposed to vault_capabilities or vault_profile, with nothing in the text confirming or excluding that.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources