Skip to main content
Glama
Sign In
viridis-agent-fleet

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

subscriptions__usage_summary

Retrieve period-resolved included and overage usage for B2B subscriptions with exact catalog lineage and conservation totals.

Instructions

[subscriptions — B2B monthly seats, entitlement quota, overage, and MRR] Return bearer-owned, period-resolved included and overage usage with exact catalog lineage and conservation totals.

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": {
      "account_id": "<account_id>"
    },
    "name": "subscriptions__usage_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.11
    • addedInput schema / properties / account_id / title
      Added value: +"Account Id"
    • addedInput schema / title
      Added value: +"usage_summaryArguments"
  2. Changed2 schema fields changedv0.1.9
    • removedInput schema / properties / account_id / title
      Removed value: -"Account Id"
    • removedInput schema / title
      Removed value: -"usage_summaryArguments"
  3. Added

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It says 'Return' which suggests read-only, but does not explicitly confirm idempotency, safety, or any behavioral traits like permissions or data freshness. For a usage summary tool, more transparency is needed.

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 sentence that fits the purpose. The bracketed prefix front-loads context. While it is somewhat dense, it avoids unnecessary words and is efficiently structured.

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 the lack of output schema, the tool's complexity (included/overage usage, periods, lineage, totals), and detailed sibling names, the description is insufficient. It does not explain return value structure, pagination, date range, or how to interpret results, leaving an agent underinformed.

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 single parameter account_id is not explained in the description. The phrase 'bearer-owned' hints that the account is tied to the bearer, but it does not clarify what identifier is expected (e.g., subscription ID, customer ID). With 0% schema coverage, the description should compensate but fails to provide sufficient meaning.

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 states it returns usage summary data (included and overage usage) with lineage and conservation totals, clearly identifying the tool's purpose. The context prefix [subscriptions — B2B monthly seats, entitlement quota, overage, and MRR] helps distinguish it from sibling tools like mrr_summary. However, jargon like 'bearer-owned' and 'exact catalog lineage' may obscure meaning.

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?

No explicit guidance on when to use this tool versus alternatives such as subscriptions__mrr_summary or subscriptions__get_plan. The description implies it is for usage summaries but does not provide context or exclusions.

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