Skip to main content
Glama

Show dashboard

show_dashboard

Show the interactive dashboard widget: balances, my coins with live positions and Phase Cred, open swap offers, watchlist, recent activity, and quick actions. Requires the user's Phase token.

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

Input Schema

NameRequiredDescriptionDefault
accessTokenNo
widgetTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses that the output is an interactive widget and that a Phase token is needed, which usefully signals a read-oriented, user-scoped display operation, but it never states whether anything is mutated, what happens when the token is missing or invalid, or how the widget behaves with live positions.

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?

Two sentences, front-loaded with the action and then the enumerated content, followed by the token prerequisite. The widget list is long but each item is a distinct content section, so it earns its space; overall efficient.

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

Completeness3/5

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

For a read-only display tool with no output schema, the content enumeration and stated token requirement cover most of what an agent needs. The unresolved gap is the two undocumented token parameters and the absence of any fallback/error behavior, which matters because neither parameter is marked required.

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 description coverage is 0% for two parameters (accessToken, widgetToken), so the description must compensate and largely does not. It mentions "the user's Phase token" in the singular without clarifying whether that maps to accessToken, widgetToken, or both, nor how the two differ - a real ambiguity given required parameters is 0.

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 a specific verb and resource ("Show the interactive dashboard widget") and enumerates the exact content sections returned: balances, coins with live positions and Phase Cred, open swap offers, watchlist, recent activity, quick actions. An agent knows precisely what this renders. It stops short of distinguishing itself from the other 'show_*' siblings, so it does not reach a 5.

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 context is only implied: the tool is the entry point for the user's dashboard overview, and a prerequisite is stated ("Requires the user's Phase token"). There is no explicit when-to-use versus show_marketplace, show_agreement, or show_coin_setup, and no when-not 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