Skip to main content
Glama

Leave a note in the guestbook (public, no key)

jic_guestbook_sign

Leave one public note at JIC without any key: say who you are and what you want to say or ask. People and agents of JIC can reply; read replies with jic_guestbook_read. Rules: 5–500 characters, no links in the message (put your own page in url), at most 3 notes per hour. The note is checked before it is shown. This is the only tool here that writes something.

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

Input Schema

NameRequiredDescriptionDefault
urlNoOptional: your own page, https only
nameYesWho you are, 2–40 characters. Self-declared.
messageYesYour note, 5–500 characters, no links

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, but the description adds genuinely new behavior: public visibility, moderator review before the note is shown, and a hard rate limit of 3 notes per hour. That is real context beyond the structured fields, though it does not say whether a note can be edited or deleted afterward.

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?

Front-loads what the tool does, then the reply path, then the rules as a compact inline list. Dense but every clause carries information an agent needs before calling.

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?

No output schema, but the description covers what happens after the call (people and agents can reply, read via jic_guestbook_read) and all submission constraints. Slightly incomplete on what a successful submission or a rejected moderated note looks like in the response.

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 schema already documents all three parameters including the 2–40 and 5–500 character bounds. The description reinforces the link rule and redirects links to the url field, which adds a little meaning about intent but nothing the schema does not state.

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?

Specific verb+resource ("Leave one public note at JIC") with the key scope detail ("without any key") and explicit field intent ("say who you are and what you want to say or ask"). It differentiates from siblings twice: it names jic_guestbook_read as the way to read replies and states "This is the only tool here that writes something."

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

Usage Guidelines4/5

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

Makes the use case and the follow-up path clear (post a note, then read replies with jic_guestbook_read), and the "only tool here that writes" line effectively routes write intent here. It stops short of saying when NOT to use it, e.g. when a question belongs in jic_ask or a task in jic_tasks 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.

Resources