Skip to main content
Glama

Handwritten signature versions

handwritten_signature
Read-onlyIdempotent

Writes a name in six handwritten hand styles for each of three name formats, full name, initial and surname, and monogram, 18 versions in all. Returns a PNG picture and an SVG for each version.

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

Input Schema

NameRequiredDescriptionDefault
inkNoInk color: green, black, blue or a six-digit hex color such as #1e3a8a. Default green.
nameYesThe name to write, 1 to 60 characters.
nameFormatNoLimits the list to one name format: full, initial-last or monogram. Default all three, 18 versions.

Output Schema

NameRequiredDescriptionDefault
kindYes
nameNo
viewYes
itemsYes
linksNo
totalYes
requestYes
pageSizeYes
nameFormatNo
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description still adds real value beyond them by disclosing the response composition: one PNG and one SVG per version, 18 versions total when no format is specified. 'Writes' here means rendering glyphs, not persisting data, which is consistent with readOnlyHint.

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 sentences, no filler, and the combinatorial scope is front-loaded before the return-value note. Every clause (six styles, three formats, 18 versions, PNG plus SVG) contributes information an agent can act on.

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?

With an output schema present, rich annotations, and fully documented parameters, the description needs only to explain scope and result shape, which it does. The one omission is routing guidance against the four sibling signature tools, which matters for selection but not for correct invocation once chosen.

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 the schema already explains name, ink (named colors or six-digit hex, default green) and nameFormat (all/full/initial-last/monogram). The description adds only the context that the default 'all' yields 18 versions, which marginally clarifies the 'all' enum value. Baseline 3 applies when the schema carries the parameter semantics.

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 names a specific action and resource ('writes a name in six handwritten hand styles') and quantifies the output ('18 versions in all... a PNG picture and an SVG for each version'). That makes the tool's job unmistakable. It stops short of 5 because it never differentiates itself from the close sibling 'make_signature' or 'signature_styles', leaving the agent to guess which generation tool to pick.

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

Usage Guidelines3/5

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

Usage is only implied: the emphasis on six styles x three formats x 18 versions signals this is the batch/variant generator rather than a single-signature tool. There is no explicit when-to-use statement, no exclusion, and no named alternative among make_signature, signature_styles, signature_ideas, or signature_practice_sheet.

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.