Skip to main content
Glama
revenium

Revenium MCP Server

Official
by revenium

business_analytics_management

Analyze business costs across providers, models, customers, and agents. Detect cost anomalies and new entities to improve cost management.

Instructions

Business analytics and cost analysis with enhanced statistical anomaly detection and new entity detection. Key actions: get_provider_costs, get_model_costs, get_customer_costs, get_api_key_costs, get_agent_costs, get_user_costs, get_tool_costs, get_top_tools, get_tool_costs_by_agent, get_tool_costs_by_provider, get_cost_summary, analyze_cost_anomalies. For anomaly detection use: min_impact_threshold, include_dimensions. For new entity detection use: detect_new_entities, min_new_entity_threshold. Use get_examples() for parameter guidance and get_capabilities() for status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoget_capabilities
breakdown_byNo
periodNo
groupNo
filtersNo
pageNo
sizeNo
thresholdNo
min_impact_thresholdNo
include_dimensionsNo
sensitivityNo
dry_runNo
example_typeNo
detect_new_entitiesNo
min_new_entity_thresholdNo
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as side effects, authentication requirements, rate limits, or data modification potential. The phrase 'enhanced statistical anomaly detection' hints at analysis but lacks detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but includes a long list of actions that could be streamlined. It front-loads the general purpose but adds redundant specifics, making it longer than necessary.

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?

Without annotations or output schema, and with 15 parameters, the description fails to provide a complete picture. It does not explain what actions do, how parameters affect results, or return values, leaving gaps for an agent to use the tool correctly.

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 coverage is 0%, so the description must compensate. It explains a few parameters (min_impact_threshold, include_dimensions, detect_new_entities, min_new_entity_threshold) but leaves most of the 15 parameters unexplained, providing insufficient guidance for correct invocation.

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 'Business analytics and cost analysis with enhanced statistical anomaly detection and new entity detection,' giving a clear general purpose. However, it does not differentiate this tool from sibling tools like manage_alerts or manage_metering, reducing clarity.

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 its siblings. The description only refers to internal sub-actions (get_examples, get_capabilities) without contextualizing when the tool is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/revenium/revenium-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server