Skip to main content
Glama
Sign In
seven-mcp

seven-mcp

Official
by seven-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_analytics

Retrieve account statistics and analytics by specifying a date range, with options to filter by subaccount, label, and group by country, date, label, or subaccount.

Instructions

Get account statistics and analytics

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_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
startNoStart date (YYYY-MM-DD)
endNoEnd date (YYYY-MM-DD)
subaccountsNoSubaccount filter: "only_main" for main account only, "all" for all accounts, or specific subaccount ID (integer)
group_byNoGroup analytics by (country, date, label, subaccount)
labelNoFilter by label

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
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 like read-only nature, data freshness, or rate limits. The tool is likely read-only, but this is not stated.

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 clear sentence, front-loading the purpose. It is concise but could include a brief usage example or note on required parameters.

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?

With 5 parameters, no output schema, and no annotations, the description is insufficient. Missing details like what analytics are returned, common use cases, or parameter interdependencies.

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 5 parameters have descriptions in the schema, providing good coverage. The tool description adds minimal value beyond the schema, such as hinting at analytics focus. Baseline score of 3 applies.

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 clearly states the tool retrieves account statistics and analytics, distinguishing it from other 'get' tools like get_balance or get_contact. However, it does not specify the scope or type of analytics, which could be improved.

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 guidance on when to use this tool versus alternatives such as get_balance (financial stats) or list_subaccounts (account listing). The description lacks context for decision-making.

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