Skip to main content
Glama
Sign In
mcp-sing

mcp-sing

by luizrodrigues034
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

test_pen_toggle

Toggles the pen up or down to control contact with paper during signature plotting on the NextDraw plotter.

Instructions

[MOVE] Cicla a caneta cima/baixo. arm_motion('test_pen_toggle',{})+token.

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": {
      "confirm_token": "<confirm_token>"
    },
    "name": "test_pen_toggle"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirm_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.6/5.0
Behavior2/5

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

The description only states that toggling occurs, with no annotations to supplement. It does not disclose whether the action is destructive, requires confirmation, or has side effects. The code snippet hints at a token requirement but lacks clarity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and includes a code snippet, which may aid developers but adds unnecessary detail. It is front-loaded with the action but could be more focused on explanation rather than code.

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?

Given the low complexity (1 parameter, no output schema) and lack of annotations, the description should provide more context about the toggle behavior, prerequisites (e.g., calibration), or typical use cases. It is insufficient for an agent to use correctly.

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 'confirm_token' has no schema description (0% coverage). The description mentions a token in the code snippet, but does not explain its purpose, format, or how to obtain it. This adds minimal value beyond the 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 'Cicla a caneta cima/baixo' clearly indicates a toggle action for the pen up/down. The verb 'Cicla' (cycles) combined with the tool name 'toggle' conveys the purpose. However, it does not differentiate from sibling tools like arm_motion, which might handle related movements.

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 such as arm_motion. There is no mention of prerequisites, context, or when not to use it.

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