Skip to main content
Glama

Sonar Connections

by com.sonarconnections
OverviewDiscussionsAdmin

Find matching attendees

event_find_matches
Read-only

Lists the people at an event the person has joined whose stated intent fits theirs. Needs a personal connector token; the event is eventId or the current one. Each row carries a first name, intent, who they are looking for, their booth if a vendor, fit and why. No row carries a phone number, email address, surname, account id or photo. Only people who chose to be findable are listed, at most 20, ordered best fit first by what each person wrote on their badge; two buyers whose lines agree are matches for each other. fit is one of three words: "strong" (most of what the caller declared is echoed on the other side), "good" (a real overlap) or "some" (a reason to be on the list and no more). why is one sentence written by the server naming the shared words, or the topic both wrote about. The reply carries no score, percentage, rating or rank. With no intent set the reply has needsIntent and no rows. An empty reply carries emptyReason and a plain message (none_findable, none_present, event_not_live or no_text_match).

Input Schema

NameRequiredDescriptionDefault
eventIdNoOptional. An event the person has joined. When absent, the event the person is currently in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / eventId / description
      Previous value: -"OPTIONAL. Omit for the event the person is currently in, which is the usual case. Only pass one if they named a different show, and it must be one they have already joined."New value: +"Optional. An event the person has joined. When absent, the event the person is currently in."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Despite annotations already marking it read-only and non-destructive, the description adds substantial behavioral detail: only opted-in people are listed, at most 20 results, ordering by fit, the exact fit vocabulary, the meaning of why, no score/percentage/rank, privacy exclusions, and emptyReason codes.

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 purpose is front-loaded in the first sentence, and the later sentences carry useful behavioral and privacy detail. It is dense and somewhat run-on, but most content earns its place for a tool with no output schema.

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 compensates by explaining returned fields, privacy limits, ordering, result caps, fit semantics, why text, needsIntent behavior, and empty-reply reasons. It is complete enough for an agent to call and interpret the tool correctly.

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% for the single eventId parameter, and the schema already explains that it is optional and defaults to the current event. The description reinforces that behavior and adds the separate connector-token requirement, but does not add much parameter-level meaning beyond the schema.

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?

The description states a specific verb and resource: lists people at an event whose stated intent fits the caller's. It clearly distinguishes this matching/list function from neighboring tools such as event_set_intent, event_say_hello, and event_send_request.

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?

It gives clear prerequisites: a personal connector token is required, the optional eventId selects an event the person has joined or defaults to the current event, and no intent produces needsIntent with no rows. It does not explicitly compare this tool to siblings or state 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 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