Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_current_user

Read-only

Identify the current user and retrieve their workspaces, identities, and settings. Use it to establish who you are acting as or to get workspace IDs before a workspace-scoped call.

Instructions

Get the calling user's own identity, workspaces and settings. USE WHEN: Establishing who you are acting as, or finding the caller’s workspace IDs before a workspace-scoped call. Takes no arguments. USE INSTEAD: get_user for somebody else (it requires an explicit ID). get_workspaces_basic_info if you only need workspace IDs and names — it is far smaller than this response. EXAMPLE: {} RETURNS: {success, user: {user_guid, first_name, last_name?, email_txt?, phone_txt?, workspace_guids, identities, entries, environments, lifecycle_events, notification_settings, settings, ...}, settings: {...}}. This payload is LARGE — several unbounded arrays and an open settings map. NARROW: pass response_fields ["user.user_guid","user.first_name","user.email_txt","user.workspace_guids"] unless you need more — the full payload is much larger.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_fieldsNoDot-path allowlist to shrink the response, e.g. ["results.id","total"]. Omit for the full payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.10.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / response_fields
      Added value: +{
+  "description": "Dot-path allowlist to shrink the response, e.g. [\"results.id\",\"total\"]. Omit for the full payload.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context beyond annotations: the response payload is LARGE with unbounded arrays and an open settings map, and it explains the NARROW mechanism to mitigate this. This is genuinely useful for an agent deciding whether to invoke and how to shape the request.

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?

The description is tightly structured with labeled sections (USE WHEN, USE INSTEAD, EXAMPLE, RETURNS, NARROW) that are each a single line or two, no filler, and the most critical scoping information is front-loaded. Every sentence earns its place.

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?

For a no-required-parameter read-only tool, this description is complete: it explains the return shape (albeit without a formal output schema, it gives a useful sketch), warns about response size, provides an example call, and routes to alternatives when appropriate. Nothing an agent needs 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?

The schema description fully documents response_fields (dot-path allowlist, example, omit for full payload). The description reinforces this with a concrete recommended list (['user.user_guid','user.first_name','user.email_txt','user.workspace_guids']) and warns about the full payload size, adding practical value beyond the schema.

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?

The description states a specific verb-resource pair ('Get the calling user's own identity, workspaces and settings') and explicitly distinguishes itself from get_user (for others) and get_workspaces_basic_info (smaller response). This makes the tool's purpose unambiguous and separable from siblings without needing to inspect schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit USE WHEN conditions (establishing identity, finding workspace IDs before workspace-scoped calls) and USE INSTEAD guidance naming two alternatives with the exact condition that selects them. This gives an agent clear routing rules, leaving nothing to inference.

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