Skip to main content
Glama

Little Works

message_listing

Open or stage a message about a listed creation (same Message surface).

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": {
      "url": "<url>"
    },
    "name": "message_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses almost nothing. 'Open or stage' hints at a dual read/write mode, but there is no statement about side effects, permissions, whether the apiKey is required at call time, whether staging is persisted, or what the response contains. 'Same Message surface' is an opaque internal reference rather than behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

It is a single short sentence, but brevity here comes from omission rather than discipline; the parenthetical adds noise while the core action stays ambiguous. There is no front-loaded statement of what the tool concretely does.

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

Completeness1/5

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

With three parameters, no annotations, and no output schema, the description is the only source of behavioral and parameter meaning, and it is insufficient on both counts. An agent would have to guess at the action's nature, its side effects, and the purpose of two of the three inputs before calling it.

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

Parameters1/5

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

Schema description coverage is only 33% — only apiKey is documented, and that documentation lives in the schema, not the description. The two undocumented parameters, url and message, get no clarification: the phrase 'a listed creation' only weakly implies url is a listing URL, and the 'message' parameter is never explained at all despite being the apparent subject of the tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Open or stage a message about a listed creation,' which gestures at a message-related action but never defines what 'open' versus 'stage' means or what a 'listed creation' is. An agent cannot tell from this text whether the tool sends a message, retrieves one, drafts one, or attaches it to a listing, nor how that differs from message-related siblings.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool, when not to, or what alternative to pick among the many list/get/buy siblings. The parenthetical '(same Message surface)' is an internal reference that gives no actionable selection criteria.

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