Skip to main content
Glama

Find a sign maker

list_signs
Read-onlyIdempotent

Lists EntryPing printable sign makers (closed, out to lunch, holiday closings, out of order, meeting in progress, QR code signs and more) with each one's default wording. Pass a few words to narrow the list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_signs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords to match against sign names, for example "thanksgiving" or "out of order". Leave out to list every sign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and a closed world, so safety is covered. The description adds relevant context beyond them: what the tool returns (each sign maker's default wording) and the breadth of the catalog. It does not discuss result volume or pagination, which keeps it from 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.

Conciseness4/5

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

Two sentences, front-loaded with the core verb and resource, with no filler. The parenthetical catalog enumeration is somewhat long but earns its place by signalling the range of signs an agent can find.

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 single, fully documented optional parameter with annotations covering safety and no output schema, the description says enough: what is listed, what is returned, and how filtering works. Only the relationship to the sibling tool is left unaddressed.

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 the query parameter is already fully documented with examples and maxLength; baseline is 3. The description adds only a light hint that a few words are enough for filtering, which is marginally beyond the schema's own wording but not substantive.

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: listing EntryPing printable sign makers, with the returned default wording and the enumerated sign categories making the domain concrete. It does not, however, distinguish itself from the sibling make_sign_link, so an agent must infer the boundary itself.

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?

The sentence 'Pass a few words to narrow the list' gives usage guidance for the query parameter and implies the unfiltered case. There is no explicit when-not-to-use, no prerequisites, and no reference to the sibling tool that would help an agent choose between finding a sign and making a sign link.

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