Soleil Clusters

Who am I

whoami

Read-onlyIdempotent

Returns the account these tools act as, its scopes (read, write, delete), whether it is a service account (confined to one workspace) and its workspaces with the ids workspace_id takes. Call it once at the start.

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": "whoami"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`scopes`	No
`user_id`	No
`workspaces`	No
`service_account`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.5/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 adds substantive context beyond that: scopes returned, service-account confinement to one workspace, and the workspace ids consumed by workspace_id elsewhere. Minor gap: it does not say what happens on an unauthenticated or expired-credential call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the return contents front-loaded and the call-timing instruction placed last where it is easy to act on. No filler or restatement of the title.

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?

An output schema exists and carries the return shape, and the annotations carry the safety profile, so the description only needs to orient the agent and state timing. It does exactly that, plus the service-account caveat an agent would otherwise have to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description still earns its place by tying the returned workspace ids to the workspace_id parameter used by other tools, which is cross-tool semantic value the schema cannot express.

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?

"Returns the account these tools act as, its scopes (read, write, delete), whether it is a service account (confined to one workspace) and its workspaces" names the specific resource and enumerates exactly what comes back. No sibling tool does anything similar, so there is nothing to confuse it with.

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?

"Call it once at the start" gives a clear when-to-use directive and a frequency constraint, which is the main guidance an identity probe needs. It stops short of saying what to do if the account or scopes change later in a session, but no alternative tool exists to route to.

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

All Soleil Clusters 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.