Skip to main content
Glama
Sign In
mcp-sing

mcp-sing

by luizrodrigues034
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

home_device

Home the pen plotter device to prepare for signature reproduction. Provide a confirm token to initiate homing.

Instructions

[MOVE] Homing. Exige arm_motion('home', {}) + 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": "home_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirm_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose behavior such as side effects, required permissions, or error handling. The mention of 'confirm_token' suggests a confirmation step, but no details are given.

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

Conciseness2/5

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

The description is very short but fails to be concise; it is ambiguous and lacks structure. It mixes English and Spanish unnecessarily, reducing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, one parameter barely described, and unclear behavioral context, the description is insufficient for an agent to use the tool correctly or safely.

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

Parameters1/5

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

The input schema has 0% description coverage, and the tool description adds no meaning to the 'confirm_token' parameter beyond its name. The description does not clarify what the token is or how to obtain it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Homing' but does not explain what homing entails. It references 'arm_motion' but the relationship is unclear, and it fails to distinguish from the sibling tool 'arm_motion'.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus alternatives like 'arm_motion' or other siblings. The description provides no context for appropriate use cases.

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