Skip to main content
Glama
Sign In
ParrotScribe MCP Server

ParrotScribe MCP Server

by johanthoren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pscribe_start

Start real-time audio transcription for microphone and system audio. Receive a status message confirming the transcription has started.

Instructions

Start real-time audio transcription (microphone and system audio). Returns status message confirming transcription started.

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": "pscribe_start"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description provides some behavioral context: it captures both microphone and system audio, and returns a status message. However, it omits whether the process runs asynchronously, how it stops, or any permission requirements, which are important gaps for a starting tool.

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?

Two sentences, front-loaded with the action, no filler. Very efficient.

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 zero-parameter tool, the description covers the action and return value. It doesn't elaborate on the workflow with sibling tools, but the simplicity of the tool makes this sufficient.

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?

Since the input schema has no parameters, the baseline is 4. The description correctly doesn't add parameter details because there are none.

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 identifies the verb ('Start') and the resource ('real-time audio transcription'), with explicit scope of 'microphone and system audio'. This distinguishes it from siblings like pscribe_stop and pscribe_status.

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

Usage Guidelines4/5

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

The context is clear: this tool starts transcription. It doesn't explicitly mention alternatives or exclusions, but the purpose is unambiguous enough that an agent would know when to use it. A 5 would require explicit 'use X instead of Y' guidance.

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