Skip to main content
Glama
Sign In
SMB AI Command Platform MCP Server

SMB AI Command Platform MCP Server

by k5tuck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

smb_get_dashboard

Retrieve data from a specific dashboard using its dashboard ID. Obtain the ID by listing available dashboards first.

Instructions

Get data from a specific dashboard. Use smb_list_dashboards first to find available dashboards.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dashboardId": "<dashboardId>"
    },
    "name": "smb_get_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
dashboardIdYesThe ID of the dashboard to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'Get data' implying a read operation, but does not disclose error conditions, permissions required, or any side effects. The description is insufficient for a tool with no annotations.

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?

Extremely concise with two sentences, no unnecessary words. Front-loaded with the core purpose, and essential usage guidance follows.

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?

No output schema and no description of what data is returned. For a 'get' tool that likely returns complex dashboard data, the description is insufficient to inform the agent about the response structure or content.

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% and the description does not add meaningful information beyond what is in the input schema. Baseline score of 3 is appropriate since the schema already documents the parameter adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Get' and resource 'data from a specific dashboard'. It clearly distinguishes from sibling tool smb_list_dashboards which lists dashboards, whereas this retrieves a specific one.

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

Usage Guidelines5/5

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

Explicitly instructs to use smb_list_dashboards first to find available dashboards, providing a clear prerequisite and usage context. This helps the agent decide when to invoke this tool.

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