Bommel Bot

list_talk

Read comments on a public Bommel. Returns factual public records and links on bommel.bot only. Not advice, not a recommendation, not an invitation to act.

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": {
      "shareId": "<shareId>"
    },
    "name": "list_talk"
  }
}

Input Schema

Name	Required	Description	Default
`shareId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

B3/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that returns are limited to factual public records and links on bommel.bot and that content is not advice, a recommendation, or an invitation to act. However, it omits operational traits such as pagination, ordering, auth requirements, and error behavior.

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 short and front-loaded with the purpose in the first sentence. The disclaimers in the final sentence are somewhat repetitive but remain concise overall.

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

Completeness3/5

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

For a simple one-parameter read tool with no annotations or output schema, the description gives only partial context. It communicates the resource and return-content constraints, but leaves shareId semantics and usage context undocumented.

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

Parameters2/5

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

Schema description coverage is 0%, and the single required parameter shareId is not explained in the description. 'Public Bommel' loosely implies shareId identifies the target, but no format, source, or validity constraints are provided.

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?

The description states a specific verb and resource: 'Read comments on a public Bommel.' An agent can tell it returns comments, but the description does not distinguish it from siblings such as get_public_bommel or search_feed.

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?

It implies the tool is for reading public Bommel comments, but gives no explicit when-to-use guidance, no conditions for choosing it over siblings, and no exclusions. The disclaimers concern content interpretation, not invocation context.

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

All Bommel Bot tools Inspect

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

Need Help?