Sonar Connections

Add an agenda, speakers or sponsors from pasted text (organizers only)

event_intake

Reads text the organizer pasted or dictated about an event they run (an agenda, a speaker or sponsor list, a flyer) and proposes the sessions, speakers, sponsors, dates and venue it found. FIRST CALL WITHOUT confirm returns a PROPOSAL with an intakeId and changes nothing; read it back, and only when the organizer says yes call again with confirm: true and that intakeId. Files are uploaded on the organizer dashboard instead. Only the organizer of the event can add to it. It requires a personal connector token.

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_intake"
  }
}

Input Schema

Name	Required	Description
`kind`	No	OPTIONAL. What the text is, when the organizer said so.
`text`	No	The pasted or dictated text. Required on the first call.
`confirm`	No	Leave out for the proposal; after a yes, true with the intakeId.
`intakeId`	No	REQUIRED with confirm: the intakeId the proposal returned.
`paletteId`	No	With templateId: one of its palette ids. For the new draft only; an existing event's colors change through event_change_detail.
`templateId`	No	Optional; a template id from the dashboard (birthday_party, quince_classic, baby_shower_soft, wedding_gallery).
`customColor`	No	Optional #rrggbb; a hard to read color is refused with the closest readable shade. For the new draft only; an existing event's colors change through event_change_detail.
`eventIdOrName`	Yes	REQUIRED. The event name as the organizer says it, or its web address.

Output Schema

Name	Required	Description	Default
`ok`	No
`code`	No
`error`	No
`counts`	No
`applied`	No
`eventId`	No
`message`	No
`preview`	No
`summary`	No
`intakeId`	No
`servedBy`	No
`sessions`	No
`speakers`	No
`sponsors`	No
`candidates`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only say it is a non-read-only, non-idempotent, non-destructive mutation. The description adds real behavioral context beyond that: the first call is side-effect free and only proposes, changes require an explicit confirm plus intakeId, only the event organizer may add, and a personal connector token is required.

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-loads the proposal/confirm contract, which is the highest-risk part, and every sentence carries information. It is dense and slightly run-on with the auth and dashboard notes trailing, but nothing is wasted.

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 8 parameters, an output schema and a two-phase workflow, the description covers everything an agent needs: what is read, what is returned on the proposal call, how to commit, who may call it, and where file uploads belong instead.

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 every parameter already carries its own documentation. The description reinforces the confirm/intakeId pairing and the no-op first call, but adds little parameter meaning the schema does not already state; baseline 3 applies.

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 — reads pasted/dictated text and proposes sessions, speakers, sponsors, dates and venue for an event the organizer runs. It reads clearly as a bulk-intake tool, distinct from event_session_add (single session) or event_create (new event).

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 sequencing: call first without `confirm` to get a proposal and `intakeId`, read it back, and only re-call with `confirm: true` after the organizer agrees. It also names an alternative path — files are uploaded on the organizer dashboard instead — so the agent knows when not to use it.

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?