Skip to main content
Glama

agentic_metrics_view

Monitor and analyze Shikigaku theory KPIs through a dedicated dashboard to track performance metrics and development progress.

Instructions

識学理論KPIダッシュボード表示

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that executes the 'agentic_metrics_view' tool. It dynamically imports fs and path modules, reads the KPI dashboard Markdown file from .ai/dashboard.md, and returns its content as a text response. If the file does not exist, it returns an error message instructing to run 'npm run dashboard:update'.
    private async handleMetricsView() {
      const fs = await import('fs/promises');
      const path = await import('path');
    
      try {
        const dashboardPath = path.join(process.cwd(), '.ai', 'dashboard.md');
        const dashboard = await fs.readFile(dashboardPath, 'utf-8');
    
        return {
          content: [
            {
              type: 'text',
              text: dashboard
            }
          ]
        };
      } catch (_error) {
        return {
          content: [
            {
              type: 'text',
              text: '⚠️ ダッシュボードファイルが見つかりません。\n\n実行: `npm run dashboard:update`'
            }
          ]
        };
      }
    }
  • server.ts:162-169 (registration)
    Registration of the 'agentic_metrics_view' tool in the TOOLS array. Includes the tool name, description ('識学理論KPIダッシュボード表示' meaning 'Display of Shishugaku theory KPI dashboard'), and an empty input schema indicating no parameters are required. This array is returned by the listTools handler.
    {
      name: 'agentic_metrics_view',
      description: '識学理論KPIダッシュボード表示',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    }
  • server.ts:244-245 (registration)
    Dispatch/registration case in the CallToolRequestSchema handler's switch statement, which routes calls to 'agentic_metrics_view' to the handleMetricsView() method.
    case 'agentic_metrics_view':
      return await this.handleMetricsView();
  • Input schema definition for the tool, specifying an empty object with no required properties.
    inputSchema: {
      type: 'object',
      properties: {}
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description only states what the tool does (display a dashboard) without mentioning any behavioral traits like whether it's read-only, requires authentication, has rate limits, or what format the display takes. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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?

The description is a single, concise phrase that directly states the tool's function. It's appropriately sized for a simple tool with no parameters, though it could be slightly more informative. There's no wasted verbiage, and it's front-loaded with the core purpose.

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?

Given the tool has no annotations, no output schema, and 0 parameters, the description is incomplete. It doesn't explain what the dashboard displays (e.g., metrics format, time range, data source), how the display is rendered (e.g., visual vs. textual), or any behavioral aspects. For a dashboard tool, users need more context about what they'll see and how it works.

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 (empty schema). The description doesn't need to explain parameters since none exist. This meets the baseline of 4 for tools with no parameters, as there's nothing to compensate for and no schema details to elaborate upon.

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

Purpose3/5

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

The description '識学理論KPIダッシュボード表示' translates to 'Shikigaku Theory KPI Dashboard Display' which indicates showing a dashboard with KPI metrics related to Shikigaku theory. This provides a general purpose (displaying a dashboard) but lacks specificity about what resources or data are involved and doesn't differentiate from sibling tools like 'agentic_kpi_collect' which might collect similar metrics.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There's no mention of context, prerequisites, or comparisons to sibling tools like 'agentic_kpi_collect' (which might collect metrics) or 'agentic_issue_analyze' (which might analyze related issues). The user must infer usage from the name alone.

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/ShunsukeHayashi/agentic-mcp-server'

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