Skip to main content
Glama

Docflare

Open the signature pad

open_signature_pad
Read-only

Shows a pad in the chat where the user draws their own signature or initials with a mouse or finger and saves it to Docflare. Use it when edit_document says the user has no saved signature or initials, or when they want to draw a new one. Once the pad says it is saved, place or fill the field with value saved.

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>"
    },
    "name": "open_signature_pad"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesWhat the user draws: the full signature or the initials.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, non-destructive, and non-openWorld, so the safety profile is covered. The description adds real context beyond that: the interaction is user-driven drawing in the chat surface, the result persists to Docflare, and the agent must wait for a saved state before acting. There is a mild surface tension between 'saves it to Docflare' and readOnlyHint, but the saving is performed by the pad/user rather than by the MCP call itself, so this reads as a UI-opening tool rather than a contradiction.

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?

Three tight sentences: what it does, when to use it, and what to do after. The most decision-relevant information (the edit_document trigger) is front-loaded after the one-line purpose statement, with no redundant restatement of the name or annotations.

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

Completeness5/5

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

Although no output schema exists, the description compensates by explaining how to interpret the result ('Once the pad says it is saved') and what to do with it ('value saved'). For a one-parameter UI-launching tool with full annotation coverage, nothing an agent needs in order to call it and act on the outcome is missing.

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% and the single enum parameter is already documented as 'the full signature or the initials'. The description mirrors that phrasing ('their own signature or initials') but adds no format, sizing, or validation detail beyond the schema. Baseline 3 is appropriate when the schema carries the semantics.

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

Purpose5/5

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

States a concrete verb and resource ('Shows a pad in the chat') plus scope ('where the user draws their own signature or initials') and the outcome ('saves it to Docflare'). An agent can immediately distinguish this from sibling open_upload_pad and from save_signature, since the drawing happens in-chat by the user.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions: use it when edit_document reports no saved signature or initials, or when the user wants to draw a new one. It also specifies the follow-up action once the pad reports saved state ('place or fill the field with value saved'), so the agent knows both entry and exit conditions.

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