Skip to main content
Glama
Sign In
masabbs-mcp

masabbs-mcp

by TatsuyaKatayama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Thread KPI

get_thread_kpi

Retrieve key performance indicators for a discussion thread and all its nested subthreads to analyze engagement and activity.

Instructions

Return KPI data for a thread and its recursive subthreads.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "get_thread_kpi"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as rate limits, authorization needs, or side effects. It only states it returns data but offers no details on what 'KPI data' includes or whether it is read-only.

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 a single concise sentence (8 words) that front-loads the purpose. Every word is necessary, and there is no wasted text.

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?

For a simple tool with one parameter and no output schema, the description covers the basic purpose and scope (recursive subthreads). It is complete enough for an agent to understand the tool's function, though additional details about the KPI data structure would enhance completeness.

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?

Schema coverage is 0%, so the description must compensate. It adds meaning by specifying that the thread_id refers to a thread and that the tool includes recursive subthreads, which goes beyond the schema's minLength constraint. However, it does not explain the parameter format or provide examples.

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 'Return KPI data for a thread and its recursive subthreads,' specifying the action (return), resource (thread and subthreads), and data type (KPI). It distinguishes from sibling tools like get_team_kpi and get_thread_context.

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 usage when KPI data is needed for a thread recursively, but lacks explicit guidance on when not to use or alternatives. No exclusions or prerequisites are mentioned.

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