Skip to main content
Glama
Connectry-io

Connectry Architect Cert

Official
by Connectry-io
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

get_dashboard

Access the study progress dashboard to view mastery levels, exam history, activity timeline, and capstone project status for certification preparation.

Instructions

Open the study progress dashboard in Claude Preview. Shows mastery levels, exam history, activity timeline, and capstone progress.

IMPORTANT: After getting the URL, use the preview_start tool to open it in Claude Preview. If the user says "show dashboard" or "open dashboard", call this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/dashboard.ts:8-33 (handler)
    The implementation of the get_dashboard MCP tool handler within the registerDashboard function.
    export function registerDashboard(server: McpServer, db: Database.Database, userConfig: UserConfig): void {
  server.tool(
    'get_dashboard',
    'Open the study progress dashboard in Claude Preview. Shows mastery levels, exam history, activity timeline, and capstone progress.\n\nIMPORTANT: After getting the URL, use the preview_start tool to open it in Claude Preview. If the user says "show dashboard" or "open dashboard", call this tool.',
    {},
    async () => {
      if (!cachedServer) {
        cachedServer = await startDashboardServer(db, userConfig);
      }

      const url = `http://127.0.0.1:${cachedServer.port}/dashboard`;

      // Also build a text summary for non-Preview clients
      const summary = buildTextSummary(db, userConfig.userId);

      return {
        content: [
          {
            type: 'text' as const,
            text: `Dashboard ready at: ${url}\n\nUse preview_start to open this URL in Claude Preview.\n\n${summary}`,
          },
        ],
      };
    }
  );
}

Tool Definition Quality

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns a URL (implied by 'After getting the URL') and requires a follow-up action with preview_start, which is useful behavioral context. However, it doesn't mention potential errors, authentication needs, or rate limits, leaving gaps for a tool that likely involves system access.

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 efficiently structured: first sentence states purpose and content, second provides critical usage instructions, third gives explicit user intent triggers. Every sentence adds value, with no wasted words, and key information is front-loaded.

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?

Given 0 parameters, no annotations, and no output schema, the description provides good context: purpose, content details, and clear usage flow. However, it doesn't explain what the URL output looks like or potential failure modes, which could help an agent handle edge cases better.

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 has 0 parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters, and it appropriately focuses on usage without redundant parameter information.

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?

The description clearly states the tool's purpose: 'Open the study progress dashboard in Claude Preview' with specific content details (mastery levels, exam history, etc.). It distinguishes from siblings by focusing on dashboard access rather than specific data retrieval like get_exam_history or get_progress. However, it doesn't explicitly contrast with all similar tools like get_progress, which might also show progress metrics.

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?

The description provides explicit usage guidance: 'After getting the URL, use the preview_start tool to open it in Claude Preview' and specifies trigger phrases: 'If the user says "show dashboard" or "open dashboard", call this tool.' This clearly indicates when to use this tool versus alternatives (preview_start for opening) and includes specific user intent examples.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Connectry-io/connectrylab-architect-cert-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server