dForms

Check the connection

whoami

Read-onlyIdempotent

Who this connection is (an API key, or a person signed in) and the workspaces it can act in, with the role in each. With a workspace to act in (the key's own, the only one, or the one workspace_id names) it also returns that workspace and the member it acts as. A quick check that the connection works.

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
`workspace_id`	No	The workspace this call acts in: an id from list_my_workspaces. Required for a person signed in with several workspaces and for staff of this deployment; optional with an API key or with only one workspace.

Output Schema

Name	Required	Description
`key`	Yes	The API key this call used, or null for a person signed in through OAuth.
`staff`	Yes	True when the person signed in is staff of this deployment: they can act in any workspace, their calls carry workspace_id, and the workspace is confirmed with the user ahead of the first read or change in it.
`member`	Yes
`person`	Yes	The person signed in through OAuth, or null for an API key.
`next_step`	Yes	The suggested next step.
`workspace`	Yes	The workspace this call acts in. Null when you signed in with several workspaces (or none) and named none.
`workspaces`	Yes	The API key's own workspace, or each one where the person is an active member. Staff can also act in any other workspace: they find it with list_my_workspaces(search).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.7/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 genuinely new behavioral context: output is conditional — the acting workspace and member are returned only when a workspace can be determined (key's own, the only one, or the one named by workspace_id). That conditional branch is not derivable from the annotations.

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 primary resource and output shape, and every sentence carries information; the parenthetical enumeration of workspace sources is slightly wordy but clarifies resolution. No filler or marketing language.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only tool with an output schema and full annotations, the description covers identity, scope, roles, and the conditional return. The only real gap is the missing disambiguation against sibling profile/workspace tools.

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 text already spells out the required/optional conditions for workspace_id, so the description mostly restates it. It adds a little resolution logic (the key's own, the only one, or the named one), but not enough to exceed the baseline when the schema already carries the semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific subject (the connection's identity: API key or signed-in person) and what is returned (workspaces plus role in each), which is concrete and distinguishable from CRUD siblings. It never differentiates itself from the nearby get_my_profile or list_my_workspaces, so an agent cannot tell from this text alone which one to reach for.

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?

"A quick check that the connection works" implies a health/identity-verification use case, and the description explains when workspace_id is needed versus optional. There is no explicit when-not or named alternative for overlapping needs (profile lookup, workspace listing), leaving routing to inference.

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

All dForms 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?