Skip to main content
Glama
WYRE-AI

avanan-legacy-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

avanan_get_daily_usage

Retrieve daily usage details across all customer tenants for a specified date, with optional MSP filtering and pagination.

Instructions

Get daily usage details across all customer tenants for a specific year/month/day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYesDay of month.
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

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only restates what the tool returns at a high level. It does not mention pagination via scrollId, whether results are read-only, permission requirements, or how the msp_ids filtering affects 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 a single efficient sentence with no wasted words and the key scoping information is front-loaded. It is concise without being padded, though it sacrifices some useful context for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given five parameters, no output schema, and no annotations, the description is too thin to be fully actionable. It omits return value shape, pagination behavior for scrollId, and clarification of how msp_ids interacts with the 'across all customer tenants' statement.

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 100%, so the schema already documents each parameter clearly. The description adds minimal extra meaning, though 'across all customer tenants' hints at the default scope when msp_ids is omitted. This meets the baseline but does not substantially exceed it.

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 clearly states the action ('Get'), the resource ('daily usage details'), and the scope ('across all customer tenants') for a specific date. This immediately distinguishes it from the sibling tool avanan_get_monthly_usage, which covers a different time granularity.

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?

The description implies the tool is for daily-level usage data, but it does not explicitly state when to use this tool over get_monthly_usage or any other sibling. There are no exclusions, prerequisites, or alternative routing guidance provided.

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