Skip to main content
Glama
Sign In
mcp-sing

mcp-sing

by luizrodrigues034
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_paper_origin

Sets the paper origin for a pen plotter by specifying the bottom-left A4 corner coordinates, enabling precise signature placement.

Instructions

Captura a origem do papel da posição ATUAL (não move). Jogue até o canto inf-esq da área plotável da A4 antes — a banda de baixo da A4 deve cair na área alcançável.

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

Input Schema

NameRequiredDescriptionDefault
a4_ref_xNo
a4_ref_yNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.1/5.0
Behavior3/5

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

The description discloses that the tool does not move the device, which is a key behavioral trait. With no annotations, it does not reveal what exactly 'captures' means (e.g., saves, affects other settings).

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 concise (two sentences) and front-loads the purpose. It earns its place but could be more structured.

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 no output schema, no annotations, and undocumented parameters, the description lacks sufficient information about return values, side effects, or parameter usage.

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?

Schema coverage is 0% and the description does not explain the two parameters (a4_ref_x, a4_ref_y) or their defaults, leaving the agent without guidance on how to specify them.

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 captures the paper origin from the current position and clarifies it does not move. However, it does not explicitly differentiate from sibling tools like calibrate_pen_paper or jog.

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 description provides explicit pre-condition instructions: position the device to the bottom-left corner of the A4 plot area before calling. It lacks explicit when-not-to-use or alternatives.

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