Skip to main content
Glama
Sign In
mcp-server-sensory

mcp-server-sensory

by jaspertvdm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

morse_timing

Convert text into precise timing data for generating Morse code audio or light signals. Specify text and base time unit in milliseconds.

Instructions

Get timing data for Morse audio/light generation

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": {
      "text": "<text>"
    },
    "name": "morse_timing"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to convert
unit_msNoBase time unit in milliseconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.9/5.0
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. It only says 'Get timing data', with no disclosure of behavior (e.g., input validation, error handling, rate limits). For a tool that likely returns structured data, this is insufficient.

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?

One short sentence, no wasted words. However, it might be too terse; a bit more detail (e.g., 'Returns a list of durations') would improve usefulness without harming conciseness.

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?

With 2 parameters, no output schema, and no annotations, the description should provide more context about return values or usage. It lacks details on what the output looks like, which is critical for an agent to interpret results.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents parameters. The description adds no extra meaning beyond what the schema provides. Baseline 3 is appropriate.

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 it 'get timing data for Morse audio/light generation', specifying the verb 'get' and resource 'timing data'. It distinguishes from sibling tools like morse_encode/morse_decode which handle actual encoding/decoding. However, 'timing data' is vague and doesn't specify what is returned (e.g., durations per symbol).

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?

No explicit guidance on when to use this tool vs alternatives like morse_encode. The description lacks context about prerequisites or typical use cases. Given sibling tools covering encoding/decoding, this omission makes it harder for an agent to choose correctly.

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