Skip to main content
Glama

Make a sign link

make_sign_link
Read-onlyIdempotent

Returns a link that opens an EntryPing sign maker with the wording already filled in. The person can edit every line and print it free or save a PDF. Nothing is 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": {
      "slug": "<slug>"
    },
    "name": "make_sign_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
subNoA short label before the time, for example "Open again".
headNoThe large main line, for example "Closed for Thanksgiving".
noteNoOne sentence under the main lines, such as a phone number or where to leave deliveries.
slugYesWhich sign maker, from list_signs, for example "closed-for-thanksgiving".
timeNoA time or date, for example "Friday at 9".
styleNoLayout. Leave out to keep the sign's own.
businessNoThe business name to print on the sign.

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 openWorldHint=false, so safety is covered. The description adds real context beyond that: 'Nothing is saved' confirms no persistence side effect, and it explains the downstream human workflow (every line editable, free printing or PDF export). Minor gaps remain, such as link lifetime or whether generating twice yields the same link.

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 short sentences, front-loaded with the return value, then the recipient experience, then the no-persistence guarantee. Every sentence carries distinct information and none restates the tool 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?

For a seven-parameter link generator with no output schema, the description usefully explains the return value (a link) and the absence of stored state, which is what an agent most needs to decide whether to call it. It could go further on link validity or whether the link is reusable, but nothing essential to correct invocation 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 description coverage is 100%, so all seven parameters already carry examples and constraints, and the enum for style is documented in the schema. The description adds no per-parameter meaning — it does not clarify how head/sub/time/note map to the printed layout beyond what the schema examples show. Baseline 3 is appropriate when the schema does the heavy lifting.

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: it returns a link that opens a sign maker with wording prefilled. The 'EntryPing sign maker' framing and the prefilled-wording outcome make the purpose unambiguous. It stops short of naming how it relates to the sibling list_signs (that link is only made in the slug parameter's schema text).

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 implied rather than stated: the description tells you what the recipient can do with the link (edit lines, print free or save a PDF) and that nothing is saved, which signals this is the non-persisting, share-with-a-person option. There is no explicit when-to-use statement, no exclusion, and no named alternative — the reader must infer that list_signs supplies the slug.

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