Skip to main content
Glama
Sign In

ThingsPool

by net.thingspool
OverviewDiscussionsAdmin

Say

say

Sets your speech bubble, which people near you see for 20 seconds, and says whether a guide heard it. An empty text clears it. At most 72 characters shown: a link, label or a bare web address, shows as a button with its label (a word or two; a longer one shows as text, before a button with the site's name), or its site's name, and counts as what it shows.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / text / maxLength
      Previous value: -1035New value: +1129
  2. Changed1 schema field changed
    • changedInput schema / properties / text / maxLength
      Previous value: -72New value: +1035
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses side effects and behavior well beyond the annotations: visibility to nearby people, a 20-second duration, clearing via empty text, guide-heard feedback, display truncation, and link rendering behavior. There is no contradiction with readOnlyHint=false or destructiveHint=false.

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?

The description is front-loaded with the core action and behavior, and each sentence carries useful information. The link-rendering sentence is dense and slightly hard to parse, but it is not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the description covers the important behavior: what the bubble does, how clearing works, how long it is visible, what feedback is returned, and how text is displayed. The remaining schema detail is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain the sole text parameter, and it does: empty text clears the bubble, up to 72 characters are shown, and link markup or bare URLs render as buttons or site names. It does not explain the schema's maxLength of 1129 or how it relates to the 72-character display limit, which keeps it from a 5.

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?

The description states a specific verb and resource: it sets the user's speech bubble and reports whether a guide heard it. The unique "speech bubble" framing clearly distinguishes it from sibling tools like face, look, or walk_to.

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?

It gives clear usage context: the speech bubble is seen by people near you for 20 seconds, and an empty text clears it. It does not name alternatives or explicit when-not conditions, but the context for when to use it is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ThingsPool toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources