Skip to main content
Glama
WYRE-AI

avanan-legacy-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

avanan_get_monthly_usage

Retrieve monthly usage details across customer tenants for a specified year and month, including per-day user counts, daily prices, and costs.

Instructions

Get monthly usage details across all customer tenants for a given year/month. Returns per-day, per-tenant rows with user count, daily price, and cost.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesYear, e.g. 2024.
monthYesMonth, 1-12.
msp_idsNoParent MSPs only: restrict usage to these child MSP IDs.
scrollIdNoPagination scroll ID from a previous response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.0
    • addedInput schema / properties / msp_ids
      Added value: +{
+  "description": "Parent MSPs only: restrict usage to these child MSP IDs.",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / scrollId
      Added value: +{
+  "description": "Pagination scroll ID from a previous response.",
+  "type": "string"
+}
  2. Addedv1.1.1
  3. Removedv1.1.0
  4. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It usefully discloses the return shape and scope, but it does not mention pagination behavior, potential data volume, access requirements, or explicitly confirm read-only behavior beyond the 'Get' verb.

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?

Two concise sentences with no filler. The verb and resource are front-loaded, and the return detail is provided in a single clarifying second sentence.

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?

The core invocation semantics and return fields are described, and optional parameters/pagination are covered by the schema. With no output schema and no annotations, it would benefit from a note on read-only behavior or data volume, but it is adequate for correct basic invocation.

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?

All four parameters already have schema descriptions, so the baseline is 3. The description does not add parameter-level detail, but the schema fully documents year, month, msp_ids, and scrollId, so no compensation is needed.

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?

The description names a specific verb (get), a clear resource (monthly usage details), and a precise scope (all customer tenants for a given year/month). It also states the return granularity (per-day, per-tenant rows), which helps differentiate it from the sibling get_daily_usage.

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 description explains what the tool does but gives no guidance on when to choose it over get_daily_usage or when to set msp_ids. There are no exclusions, prerequisites, or alternative routing hints.

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

Deploy Server

Other Tools