Returns the Swarmtix organisation and organizer account a connection acts for, and the permissions it was granted

swarmtix_whoami

Returns the organisation and the organizer account this connection is acting for, plus the list of scopes it was granted. It takes no arguments and touches nothing.

When you would reach for it

To confirm which organisation you connected. One authorized connection covers exactly one organisation, and the organisation is fixed inside the token rather than passed in on each call. If you belong to several, this is the tool that tells you which one this connection landed on.
To find out what the assistant may actually do. grantedScopes is the authoritative list. A capability you expected and cannot find is almost always a scope you did not approve.
As a cheap connectivity check. It is the only tool with no parameters, so it fails for exactly one reason: the connection itself.

Scope

profile

Every connection includes it. It exposes your name, your email address and the organisation this connection covers — nothing about events, orders, attendees or money.

Parameters

None. The tool takes no arguments at all.

The organisation and the organizer are read from the access token's claims. There is deliberately no parameter for either: a tool that accepted an organisation id would let a caller holding a valid token for one organisation ask about another.

Example call

{
  "name": "swarmtix_whoami",
  "arguments": {}
}

What comes back

{
  "organization": {
    "id": "e3a58c71-6b04-4d29-9f8e-2c71a05b4d63",
    "name": "Northwind Events",
    "url": "northwind-events"
  },
  "user": {
    "id": "1d7f4b90-2c85-4e63-a018-9b5d6f2a3c47",
    "name": "Sam Okafor",
    "email": "[email protected]"
  },
  "grantedScopes": [
    "analytics:read",
    "events:read",
    "events:write",
    "orders:read",
    "profile"
  ]
}

Field	What it is
`organization.id`	The organisation this connection is bound to
`organization.name`	Its display name
`organization.url`	Its public URL slug on Swarmtix
`user.id`	The organizer account the connection authorizes as
`user.name`	That account's full name
`user.email`	That account's email address
`grantedScopes`	Every scope approved on the consent page, alphabetically

grantedScopes is sorted, so two calls produce the same order and a diff between them is real.

What happens when you call it

The organisation id and the organizer id are read from the access token, not from your request.
The organisation row is looked up and three named fields are projected from it.
The organizer's account row is looked up and three named fields are projected from it.
The scopes on the token are sorted and returned.

If either lookup finds nothing — a deleted account, an organisation that has gone — that half of the response is null rather than an error, and the other half still answers.

The projection is explicit on purpose. A field reaches you only because somebody typed its name into this tool. That is the same rule that keeps ticket barcodes and security codes out of every tool in the catalog.

Troubleshooting

"This connection is not carrying a Swarmtix organizer and organisation. Reconnect to Swarmtix and authorize again."

The token reached the server but does not carry the claims a tool needs — no organizer, or no organisation, or neither. This is not a missing permission and not a bad argument; the credential itself is unusable. Reconnect from your client's settings and approve the consent page again.

"This connection is not authorized for `profile`. Reconnect and grant it to use this tool."

profile was not approved. Every connection normally includes it, so this usually means a hand-rolled client asked for a narrower scope set. Reconnect and approve profile.

The organisation is not the one you expected

The organisation is chosen at approval time and cannot be changed afterwards. Revoke the connection in Settings → Developers → Connections and authorize a new one against the right organisation. To use two organisations at once, connect twice — most clients let you add the same server under two names.

`grantedScopes` is shorter than you thought you approved

What the tool reports is what the token carries, which is what the consent page actually granted. Some clients request a reduced scope set on a re-authorization. Revoke and reconnect, and read the permission list on the consent page before clicking Allow.

Use cases

Sanity check after setup — one call that proves the connection works end to end
Picking between two connections — when the same server is added twice for two organisations
Explaining a missing tool — compare grantedScopes against the scope column in the tool reference
Support requests — the organisation id here is the one to quote

swarmtix_whoami

On this page