Skip to main content
Glama

Reports and analytics

portal_reports_get
Read-onlyIdempotent

Your client-portal Reports & Analytics exactly as /portal/reports shows it, for the signed-in account only: key numbers (requests, orders, spend and outstanding per currency, quoted, certificates, active projects), request/project status counts, an activity time series, and a per-service breakdown. Filter by date range (30d, 90d, 12m, ytd, all or custom from/to), service and project. Money is reported per currency (currencies are not mixed);services without prices return null amounts (not zero). Sections report their own errors; a filter that does not apply to a section is listed in ignored_filters and that section's numbers are omitted, not shown unfiltered.

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd day, inclusive (custom range). At most 731 days.
fromNoStart day (custom range).
rangeNoDate preset. Default 90d. custom needs from and to.
localeNoLanguage of project titles. Default en.
projectNoOne of your project codes (see portal_reports_options).
serviceNoLimit to one service group.
sectionsNoSections to return. Default: all.
granularityNoTime bucket size. Default auto.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, and the description still adds substantive behavior beyond them: per-currency money that is never mixed, null (not zero) amounts for unpriced services, per-section error isolation, and ignored_filters causing a section's numbers to be omitted rather than shown unfiltered. It does not cover return shape or size limits, keeping it below a 5.

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?

Scope and contents are front-loaded in the first clause, then behavioral caveats follow in a logical order with no filler. It is dense and slightly run-on (a stray semicolon before 'services without prices'), but every sentence carries information.

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

Completeness5/5

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

With eight optional parameters, no output schema, and no required fields, the description does the work of the missing output schema by naming the returned sections and their contents, plus the per-currency and error-isolation semantics. An agent has enough to invoke it correctly and interpret the response.

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 eight parameters are already documented, and the description largely restates the range presets and the service/project filters. Its one genuine addition is the rule that a filter not applicable to a section surfaces in ignored_filters and suppresses that section's numbers, which is meaningful but narrow.

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 gives a specific verb-and-resource framing ('Reports & Analytics ... for the signed-in account only') and enumerates the payload (KPIs, status counts, activity series, per-service breakdown), so an agent knows exactly what it returns. It stops short of naming which sibling to prefer instead (portal_reports_options, portal_dashboard_get), so it is clear but not sibling-differentiated.

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?

Usage is implied rather than stated: the agent can infer 'use this to read the reports page' and the description explains filter behavior (30d/90d/12m/ytd/all/custom), but it never says when to choose this over the options or dashboard tools, nor any prerequisites. That is minimum-viable guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources