Sonar Connections

Show my business card

event_my_card

Read-onlyIdempotent

Shows the person's own business card for an event, the card a booth scan or a badge swap hands over: their first and last name, title and company, their LinkedIn link when their card carries one, the event's name, and their pass QR, which the Sonar Connections web scanner reads off the screen. The back lists the people they swapped cards with (first name and company, where and when), and for a person who staffs a booth, the booth's name, its staff first names and its raffle, drop and side-event titles. Clients that show cards draw it; the same card also comes as text. Needs a personal connector token. The event is eventId when given, otherwise the person's current event.

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

Input Schema

Name	Required	Description	Default
`eventId`	No	Optional. Event id, public slug or event name. When absent, the person's current event; with no current event, the card is drawn without an event and without a pass QR.

Output Schema

Name	Required	Description	Default
`ok`	No
`qr`	No
`code`	No
`booth`	No
`brand`	No
`error`	No
`event`	No
`found`	No
`metAt`	No
`person`	No
`source`	No
`cardUrl`	No
`message`	No
`servedBy`	No
`metAtCount`	No
`suggestions`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral value: the dual render/text output mode, the auth requirement (personal connector token), and the documented fallback that with no current event the card is drawn without event metadata and without a pass QR.

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 card's purpose, then contents, then fallback and auth. The middle clause listing back-of-card fields is dense and comma-heavy, but every element describes something the caller will actually see, so little 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 an output schema present, the description needn't specify return shapes, and it nonetheless covers rendering mode, auth, and the no-event degenerate case. For a zero-required-parameter read tool this is sufficient to call 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 optional parameter and the schema already explains the absent/current-event fallback, so the description's closing sentence largely restates it. No added semantics such as accepted id formats beyond what the schema lists.

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?

Specific verb and resource ('Shows the person's own business card for an event'), followed by the exact contents of the card front (name, title, company, LinkedIn, event name, pass QR) and back (swaps, booth details). An agent can distinguish this from a generic event lookup 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 Guidelines3/5

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

It gives useful operating context – that clients render the card, that the same card is also available as text, and that a personal connector token is required – but it never states when to prefer this over lookalike siblings such as events_personal_card or events_floor_card. Usage is implied by the description rather than routed.

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?