Skip to main content
Glama

Signature styles

signature_styles
Read-onlyIdempotent

Lists the 24 signature styles with the name written in each, filterable by elegant, casual or bold. Returns a picture of the name in every style and a link to open each style on Signature Maker.

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

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.
groupNoStyle group to list: elegant, casual, bold or all. Default all.

Output Schema

NameRequiredDescriptionDefault
kindYes
nameNo
viewYes
groupNo
itemsYes
linksNo
totalYes
requestYes
pageSizeYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds that results include an image per style and an external 'Signature Maker' link, which is useful but overlaps with the existing output schema rather than disclosing anything an agent could not already see; nothing is said about result size or cost of rendering 24 images.

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, front-loaded with the resource and count, then the return shape. No filler, no repetition of the title.

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 and full input-schema coverage, the description only needs to orient the agent, which it does well. A small gap remains: it does not say how the ink parameter affects the returned images or whether all 24 styles are returned when group is 'all'.

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%, so name, group and ink are all documented in the schema including the enum and hex format. The description only restates the group filter values and the fact that name is written into each style; it adds no new semantics such as how ink interacts with the rendered preview.

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?

States a specific verb and resource ('Lists the 24 signature styles'), including the exact count, the filterable groups, and what comes back (a rendered image plus a link per style). It is clear what the tool produces, but it never distinguishes itself from siblings like signature_ideas or make_signature, so an agent must infer the boundary.

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: an agent can infer you call this to preview a name across all styles before picking one. There is no explicit 'use this when…' clause, no exclusion, and no mention of when to prefer make_signature or signature_ideas instead.

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.