Skip to main content
Glama
Sign In
@runehand/mcp-server

@runehand/mcp-server

by echelonlabs-sf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get analytics dashboard

get_analytics

Retrieve workspace KPIs and quick stats for a date range, mirroring the in-app dashboard data.

Instructions

Get workspace KPIs and quick stats for a date range, same data as the in-app dashboard.

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

Input Schema

NameRequiredDescriptionDefault
toNoRange end (YYYY-MM-DD). Defaults to today.
fromNoRange start (YYYY-MM-DD). Defaults to 30 days before "to".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry full burden. It indicates a read-only analytics retrieval ('Get workspace KPIs') and references the in-app dashboard but does not disclose permission requirements, rate limits, pagination, or whether the response is a single report or a stream of data.

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?

The description is concise and front-loaded with the verb and resource. It wastes no words and includes a useful clarifying note about being the same data as the in-app dashboard.

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?

This is a simple read-only tool with fully documented date parameters, but it lacks explicit information about the output structure or metrics returned. Since there is no output schema and no annotations, the description's vague 'KPIs and quick stats' leaves some ambiguity about what the agent can expect.

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%, already documenting both 'from' and 'to' date params with defaults. The description only says 'for a date range', adding no new parameter semantics beyond what the schema provides.

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 clearly states the verb 'Get' and the specific resource 'workspace KPIs and quick stats for a date range'. This distinguishes it from all sibling tools, which focus on bots, flows, conversations, conversations, or leads.

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?

The description implies this tool is used to retrieve workspace analytics for a date range but provides no explicit exclusions or alternative tool recommendations. The phrase 'same data as the in-app dashboard' gives some context but doesn't clearly specify 'when to use this vs. something else'.

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