Skip to main content
Glama
Sign In
NitroStack Calculator MCP Server

NitroStack Calculator MCP Server

by Rookie-1207
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

extract_commitments

Extract commitments from meeting transcripts to capture action items and follow-ups.

Instructions

Extract commitments from a meeting transcript

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": {
      "transcript": "<transcript>"
    },
    "name": "extract_commitments"
  }
}

Input Schema

NameRequiredDescriptionDefault
transcriptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the basic action. It fails to mention expected output format, assumptions about transcript structure, or potential limitations (e.g., language support, commitment definition), leaving significant behavioral unknowns.

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 that is immediately understandable. It contains no redundant information and is front-loaded with the action verb, making it highly scannable.

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?

The tool has no output schema or annotations, yet the description does not explain what the extraction result looks like or how it should be interpreted. For a tool with a single input, this is a significant gap—the agent cannot anticipate the response structure or downstream usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'transcript' has 0% schema description coverage, and the tool description adds no extra context about the expected format, language, or length. It merely echoes the parameter name, providing no value beyond the schema's type declaration.

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 tool's function with a specific verb ('extract') and resource ('commitments from a meeting transcript'). It distinguishes itself from sibling tools like 'calculate' and 'convert_temperature' by specifying domain and output concept, and from 'get_commitments' by implying extraction from a transcript rather than retrieval.

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 a meeting transcript is available and commitments need to be identified. However, it does not explicitly state when to prefer this over 'get_commitments' or any other alternative, leaving the decision to the agent's inference.

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