Skip to main content
Glama

get_dashboard_summary

Read-onlyIdempotent

Retrieves a raw cross-workspace rollup of unread items and task buckets, giving agents a dashboard view for workload and unread activity.

Instructions

Raw cross-workspace rollup (unread + task buckets). Prefer list_workspaces, which is the same data, cleaned up.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds one genuinely useful trait beyond that, that the payload is raw versus the cleaned-up sibling, but says nothing about latency, aggregation scope limits, or which workspaces are included.

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?

Two short sentences, zero filler, and the resource description is front-loaded before the alternative. Every clause carries information the agent needs.

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 zero parameters, full annotation coverage, and an output schema handling return values, the description only needs to state purpose and routing, which it does. The minor gap is that the deprecation-like framing is implicit rather than stated outright.

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?

The tool takes no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 concretely what the tool returns: a raw cross-workspace rollup containing unread counts and task buckets. It explicitly distinguishes itself from list_workspaces by framing itself as the unfiltered/unpolished variant, so an agent can tell them apart, though 'raw' and 'task buckets' are only loosely defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing instruction: prefer list_workspaces because it returns the same data cleaned up. That is a clear when-not-to-use signal, but it never states the conditions under which this tool is still the right choice (e.g., needing raw shape or legacy compatibility).

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