Sonar Connections

Close a vote (hosts and organizers only)

event_vote_close

Closes a vote and, unless announce is false, sends one notice with the winning option, all tied options on a tie. quiet true sends it with no lock-screen alert. Hosts and organizers only.

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": {
      "eventIdOrName": "<eventIdOrName>"
    },
    "name": "event_vote_close"
  }
}

Input Schema

Name	Required	Description
`quiet`	No	True: the notice carries no lock-screen alert.
`voteId`	No	The vote; the latest when absent.
`confirm`	No	Absent previews the winner; true closes the vote.
`announce`	No	Default true: one notice with the winner. False closes without one.
`requestId`	No	Optional caller id; one id closes once.
`eventIdOrName`	Yes	The event id or name as the organizer spells it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations (which only say non-read-only, non-destructive, non-idempotent), the description discloses meaningful behavior: exactly one notice is sent, ties announce all tied options, announce=false suppresses the notice, and quiet=true removes the lock-screen alert. The remaining gap is that it never mentions the preview-on-absent-confirm behavior, which is the most consequential hidden trait for a mutating tool.

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 mutating behavior and its exception are front-loaded in the first sentence, with qualifying details after. Slight awkwardness in "all tied options on a tie" costs a point but there is no filler or repetition.

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?

For a 6-parameter mutation with no output schema, the description covers the side effects and authorization well enough to call safely. The one substantive omission is the confirm-based preview path, which an agent would only learn from the schema.

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 description coverage is 100%, so announce, quiet, and voteId are already fully documented in the schema; the description restates announce and quiet rather than adding new meaning. The baseline of 3 is appropriate when the schema carries this much of the load.

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 ("Closes a vote") plus its principal side effect (one notice with the winner), which lets an agent distinguish it from event_vote_open and event_vote_results by name alone. It stops short of explicitly naming those siblings as alternatives, so it is clear but not fully differentiated in text.

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

Usage Guidelines3/5

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

"Hosts and organizers only" supplies a real authorization precondition, which is the strongest guidance offered. However, there is no explicit statement of when to call this rather than event_vote_results, nor a note that the vote must already be open, leaving usage to be inferred from context.

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

All Sonar Connections 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?