Skip to main content
Glama

Docflare

Save a drawn signature

save_signature
Idempotent

Saves what the user drew on the signature pad as their signature or initials, replacing the one saved before. Only the signature pad calls this.

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": {
      "type": "<type>",
      "image": "<image>"
    },
    "name": "save_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesWhich one the user drew: the full signature or the initials.
imageYesThe drawing as a PNG data URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false and idempotentHint=true, and the description adds the key behavioral fact those annotations do not convey: the saved signature 'replac[es] the one saved before', i.e. it overwrites prior state. It also discloses the invocation channel. What is missing is the failure/validation behavior (e.g. what happens to an existing signature if the save fails), so it is not a 5.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and overwrite semantics, followed by the caller restriction. Nothing is redundant with the title or padding.

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

Completeness4/5

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

For a simple two-parameter persistence tool with full schema coverage and meaningful annotations, the description covers purpose, overwrite semantics, and invocation context. Most of what an agent needs in order to call it correctly is present, with only return/failure behavior left unstated.

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 description coverage is 100%, so both parameters are already fully documented (the enum meaning and the PNG data URL format). The description restates the signature/initials distinction but adds no format, size, or encoding detail beyond the schema, which is the expected baseline when the schema carries the load.

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 gives a specific verb and resource ('Saves what the user drew on the signature pad as their signature or initials') and scopes it to two variants, so an agent can distinguish it from open_signature_pad, which opens the pad rather than persisting a drawing. It stops short of naming that sibling explicitly, but the caller note ('Only the signature pad calls this') implicitly separates the two.

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?

'Only the signature pad calls this' is a real usage constraint: it tells an agent this is a UI-driven callback rather than a tool to invoke on its own initiative. That is an effective when-not-to-use signal, though no explicit alternative is offered for agents that want to initiate a signature flow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources