Skip to main content
Glama

Portal dashboard

portal_dashboard_get
Read-onlyIdempotent

Your client-portal dashboard exactly as the /portal page shows it, for the signed-in account only: key numbers (open requests, active orders, valid certificates, AI connections, unpaid orders…), recent activity, notifications and alerts, and an account overview. Each section can fail on its own (status "error"). Free text is wrapped as data.

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

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage of notification titles. Default en.
sectionsNoSections to return. Default: all four.
activity_limitNoHow many recent-activity items (1-20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the lower bar applies. The description still adds real value: each section can independently fail with status "error", and free text is wrapped as data (a prompt-injection safeguard the agent would otherwise not know about). Scope is also pinned to the signed-in account.

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?

Front-loaded with the core identity and scope in the first clause, then enumerates contents, then two short caveats. No filler, though the contents list is slightly long relative to the caveats that matter most for correct use.

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?

With no output schema, the description carries the burden of explaining the return shape and does so by naming the four sections and the per-section error status. It omits anything about notification title language or activity counts, but those are already in the schema.

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 coverage is 100%, so locale, sections and activity_limit are fully documented in the schema with defaults and bounds. The description adds no additional meaning about these parameters, so the baseline 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?

Names the concrete resource (the client-portal dashboard mirroring the /portal page) and enumerates what it contains: KPIs, recent activity, notifications/alerts, account overview. This distinguishes it well from granular siblings like portal_invoice_get or portal_invoices_list, though it never explicitly names an alternative.

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 by 'exactly as the /portal page shows it' and 'for the signed-in account only', which tells the agent this is the aggregate overview call. There is no explicit statement of when to prefer this over the more granular portal_* tools, nor any exclusion case.

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