Skip to main content
Glama

Who am I

whoami
Read-onlyIdempotent

Return the authenticated Clera user: email, organization memberships, the account kind (admin, company member, recruiter, candidate, or none), what setup steps remain and the guide for this account's tools. Read the guide first. When setup is not empty, work through the items with the relevant tools before moving on.

Clera privately records this tool's inputs and results for usage tracking and support.

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

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
emailYes
guideYesClera's playbook for the tools this account has. Read it before any other call and follow it.
setupYesWhat is still incomplete. label: the step in plain language. route: the tool (with field or command) that completes it, or null. Empty when fully set up.
accountYesadmin: full access across Clera. company_member: belongs to at least one company, the company tools apply. recruiter: a Clera partner recruiter; the guide names their tools. candidate: a Clera candidate account; the dashboard tools apply — searchCleraRoles (roles Clera can introduce them to, always first), listMatches, likeMatch, declineMatch, listMyPipeline, readPreferences, editPreferences, listResumes, listInterviewRequests, getInterviewPrep, getTalentDashboardLink and the external job board (searchJobs, saveJob, listSavedJobs) and the application tracker (listApplications, readApplication, trackApplication, updateApplication, deleteApplication, generateApplicationDocuments). none: a Clera login connected to neither.
organizationsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false, openWorldHint false), so the description's marginal contribution is the note that inputs and results are recorded for usage tracking and support, plus the fact that the response drives setup routing. It does not say what happens when unauthenticated or how the guide is structured. Useful but not rich behavioral context.

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 return payload, then the action instruction, then a separate privacy disclosure. Every sentence carries information, though the tracking/support sentence is boilerplate that could be inferred from a policy page rather than a tool doc.

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, yet the description still summarizes the key response fields and, more importantly, tells the agent how to act on the setup data it receives. For a zero-parameter identity/bootstrap tool, nothing needed to call it correctly is missing.

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?

Zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The description correctly avoids inventing inputs.

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?

States a specific verb and resource ("Return the authenticated Clera user") and enumerates the payload: email, organization memberships, account kind with the full enum of values, remaining setup steps, and the tool guide. This distinguishes it cleanly from every domain sibling, which act on jobs, resumes, or interviews rather than identity.

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?

Gives explicit sequencing: "Read the guide first" and "When setup is not empty, work through the items with the relevant tools before moving on." That tells the agent both when to call it and what to do with the result. It stops short of naming a specific alternative tool for the setup items, but the branching condition is clear enough to act on.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources