Skip to main content
Glama

Sonar Connections

by com.sonarconnections
OverviewDiscussionsAdmin

Read the guests' requests (hosts only)

event_guest_requests
Read-onlyIdempotent

THE HOSTS' OWN LIST of what their guests have asked for on a personal event this connector serves. Call it for "what have our guests asked for", "any dietary requests", "who needs anything". It returns the OPEN requests, newest first, each one as a category, the note the guest wrote, who it is from and when it landed. ONLY THE HOSTS can read it; anybody else gets a refusal you read out as given. WHO IT IS FROM IS A FIRST NAME OR THE WORDS "a guest", and there is no phone number, no email address and no account id on this surface at all, so never offer to contact somebody from this list. Read the notes out as given and do not summarise a need into something the guest did not say. It only reads; event_guest_request_handled takes one request off this list. It requires a personal connector token.

Input Schema

NameRequiredDescriptionDefault
eventIdOrNameYesREQUIRED. The event id or the event NAME as the hosts spell it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / markHandled
      Removed value: -{
-  "description": "OPTIONAL. The `id` of one request, exactly as a row from this same tool gave it. Never construct one. It marks that request handled so it leaves this list; it messages nobody and changes nothing on the event.",
-  "maxLength": 200,
-  "type": "string"
-}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (which already declare readOnly/idempotent) by disclosing hosts-only authorization with a refusal path, an open-requests-only filter, newest-first ordering, and the exact fields returned. It also flags the PII boundary (first name or 'a guest', no phone/email/account id) and instructs verbatim handling of notes — real behavioral guidance an agent cannot get from structured fields.

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 resource identity and return shape before the constraints, and nearly every sentence carries operational guidance. The all-caps emphasis and the repeated verbatim-handling instruction in the last third are slightly verbose, but nothing is truly 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 no output schema, the description fully specifies the return shape (category, guest note, first-name sender, timestamp, open-only, newest first), the authorization model, and how to handle refusals. Nothing an agent needs in order to call and report on this tool is missing.

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 coverage is 100% and the schema already says the parameter accepts an event id or the event NAME as hosts spell it. The description adds only the framing that the event is a personal event this connector serves; no additional format or lookup semantics.

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 ('the hosts' own list of what their guests have asked for') and scopes it to a personal event on this connector, which separates it from the sibling event_requests and event_inbox. An agent can identify what it retrieves without opening the schema.

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

Usage Guidelines4/5

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

Gives concrete trigger phrases ('what have our guests asked for', 'any dietary requests') and names event_guest_request_handled as the follow-up action for clearing an item. It doesn't explicitly exclude event_requests or event_inbox, so the boundary with those siblings is left to inference.

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

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