Skip to main content
Glama
Sign In

VivaDialog

by com.vivadialog
OverviewDiscussionsAdmin

Get usage

get_usage
Read-onlyIdempotent

Show this period's usage against the plan: conversations, AI replies, automations, connected channels and add-on balances, with a forecast of what runs out first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds real value beyond that by disclosing the scope of returned data and the presence of a forecast of what exhausts first – a behavioral trait not visible in any structured field. It stops short of noting whether the period is fixed billing-cycle or how balances are computed.

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?

A single dense sentence that is front-loaded with the core action ('Show this period's usage against the plan') and then lists the returned metrics. Nothing is redundant and no sentence lacks purpose.

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?

For a no-param, no-output-schema tool, the description adequately conveys what comes back, including the forecast element. A minor gap remains around the period definition and whether results are account-wide versus per-workspace, which an agent might need when interpreting numbers.

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

Parameters4/5

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

Zero parameters, so the baseline of 4 applies; the schema is trivially complete. There is nothing for the description to compensate for, and it correctly describes a parameterless snapshot call.

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?

States a specific verb and resource ('Show this period's usage against the plan') and enumerates exactly which metrics are returned: conversations, AI replies, automations, channels, add-on balances, plus a forecast. This clearly separates it from get_plan (plan definition) and get_inbox_analytics (inbox-specific metrics), though it never names those siblings explicitly.

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 usage context is implied ('against the plan', 'what runs out first'), so an agent can infer this is the quota/billing-health check. However, there is no explicit statement of when to call it versus get_plan or get_inbox_analytics, and no prerequisites or exclusions are given.

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

All VivaDialog toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources