Sonar Connections

List your unpublished drafts (hosts)

event_draft_list

Read-onlyIdempotent

Lists the signed-in person's own unpublished drafts, as the organizer dashboard's draft list does: for each its eventId, name, kind, createdAtMs and lastActivityAtMs, newest activity first, at most 20, with openDrafts and the cap (5 unpublished drafts per verified phone). Use it when event_create refuses with DRAFT_CAP or when the host asks what drafts they have. A published event does not appear. It requires a personal connector token.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "event_draft_list"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ok`	No
`cap`	No
`code`	No
`count`	No
`error`	No
`drafts`	No
`message`	No
`servedBy`	No
`openDrafts`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real behavioral context: ordering by newest activity, a hard page size of 20, the per-verified-phone cap of 5 with an accompanying cap field, and the requirement of a personal connector token. The only gap is pagination/truncation behavior when a host somehow exceeds 20 drafts.

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 verb and scope, then triggers, then constraints — a sensible order with no filler. The opening sentence is long and packs the field list, ordering, and cap into one run-on clause, and the field enumeration partly duplicates the output schema, costing a little tightness.

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 zero-parameter read tool with an output schema, an agent needs only to know when to call it, what it will and won't contain, and any auth prerequisite — all three are present, including the personal connector token note. Nothing material is left to inference.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics for the description to clarify. It does not confuse the reader by implying optional filters exist.

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 ('Lists the signed-in person's own unpublished drafts') and bounds the scope with 'own' and 'unpublished', which cleanly separates it from the published-event siblings like events_list and event_organizer_overview. It even names the shape of what comes back (eventId, name, kind, createdAtMs, lastActivityAtMs) so the agent knows this is a draft registry, not an event feed.

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 two explicit triggering conditions: recovery from event_create returning DRAFT_CAP, and a host asking what drafts exist. It also states a negative case ('A published event does not appear'), which prevents the agent from reaching for this when it actually wants published events.

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?