Skip to main content
Glama

Get user details

crunch_get_user_details
Read-only

Retrieve the logged-in Crunch user's ID, email address, first name, and last name to identify the current account.

Instructions

Get the logged-in Crunch user: ID, email address, first and last name.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the field list returned. It does not mention what happens when no user is authenticated or whether an auth flow (crunch_auth_start/status siblings) must precede it, which is the main behavioral unknown for a session-scoped tool.

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 resource stated first and the returned fields trailing; no filler and nothing to trim.

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 no-parameter read with no output schema, enumerating the returned fields in the description is the right compensating detail, and annotations cover the safety profile. The only gap is the unstated authentication precondition given the presence of companion auth tools.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies.

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 ('Get the logged-in Crunch user') and pins down the scope as the authenticated user rather than any client or supplier record, which is exactly the distinction needed against siblings like crunch_get_client. It also enumerates the returned fields, so an agent knows what it will receive before calling.

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?

The phrase 'logged-in Crunch user' implicitly scopes usage to the current session and signals this is not a lookup-by-ID tool, which is decent guidance for a zero-parameter call. However, it names no alternative and gives no exclusion for cases where a client or supplier record is actually wanted.

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

Deploy Server

Other Tools