Suumer

Tell Suumer a listing is wrong

report_listing_problem

Idempotent

Use when the person says a Suumer listing is wrong (the time changed, it was cancelled or moved, the place is wrong, it is not open to the public) and wants Suumer told, or agrees when you offer. Sends one report to Suumer's review queue holding only the listing and which part is wrong, picked from a fixed list: no note, name, email or account is sent or kept. A person at Suumer checks the listing against its source; nothing on the listing changes by itself. Take the listing from the suumerPage of a find_events result. The same report sent twice in a day counts once.

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": {
      "listing": "<listing>",
      "problem": "<problem>"
    },
    "name": "report_listing_problem"
  }
}

Input Schema

Name	Required	Description	Default
`listing`	Yes	The listing's Suumer page (https://suumer.com/e/...) or its id.
`problem`	Yes	Which part is wrong: wrong_facts = the name, time, or other facts are wrong; cancelled_or_moved = it was cancelled or moved; wrong_place = the place or address is wrong; not_a_public_event = it is not a public event; other = something else is wrong.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well past the annotations: it discloses exactly what data leaves the conversation (only listing + problem, no note, name, email or account kept), that a human reviews it, that nothing on the listing changes automatically, and that duplicate reports in a day collapse to one — which concretely explains the idempotentHint. For a mutation-flavored tool with readOnlyHint=false, this is the privacy and side-effect context an agent needs.

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?

Front-loaded with the trigger, then what is sent, what happens, where the listing comes from, and dedupe — every sentence carries distinct information. It is dense with clauses and parentheticals, so it reads slightly long for a two-parameter tool, but nothing is filler.

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?

With no output schema, the description supplies the outcome the agent would otherwise lack: a report enters a review queue, a person at Suumer verifies it against the source, and the listing itself is unchanged. Privacy handling and dedupe behavior round out the picture.

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 100%, so the schema already defines both params and the enum values. The description still adds value by tying the enum to natural-language user complaints ("the time changed", "it is not open to the public") and by specifying where the listing value comes from (suumerPage of a find_events result).

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?

States a specific verb and resource — sends a report about a Suumer listing that is wrong — and enumerates the failure kinds it covers (time changed, cancelled/moved, wrong place, not public). It also names the sibling find_events as the source of the listing, so the agent can separate reporting from searching.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions: the person says a listing is wrong and wants Suumer told, or agrees when offered. It also gives the upstream dependency (take the listing from the suumerPage of a find_events result), which is the only alternative path an agent would need.

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

All Suumer 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?