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

mcp-server-sensory

by jaspertvdm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

braille_binary_grid

Generate a binary grid from text for use in punchcards, CNC, or laser cutting. Provides machine-readable and tactile output.

Instructions

Generate binary grid for machine-readable punchcard or CNC/laser cutting

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

Input Schema

NameRequiredDescriptionDefault
textYesText to convert

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?

With no annotations, the description carries the burden of behavioral disclosure. It only states a generation action, omitting side effects, output format, constraints (e.g., text length), or auth requirements. The agent cannot infer important traits.

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 efficient sentence that communicates the core purpose. While concise, it lacks structure like a summary sentence or breakdown, but it is not verbose.

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?

Without an output schema or annotations, the description does not clarify what the tool returns (e.g., string, image, data). This gap makes it difficult for an agent to correctly handle the output.

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% for the single 'text' parameter, which has a straightforward description. The tool description adds no further semantics or constraints, achieving only the baseline for a well-documented schema.

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 the action ('Generate binary grid') and target contexts ('machine-readable punchcard or CNC/laser cutting'), which distinguishes it from encoding/decoding tools. However, it does not explicitly differentiate from the sibling 'braille_punchcard'.

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 guidance is provided on when to use this tool versus alternatives like braille_encode or braille_punchcard. The description implies usage for physical production but offers no exclusions or context.

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