agent4.io

get_end_user

Get one end user's detail: basic profile (name, contact email/phone, city, timezone) + their spaces.

Never any conversation content. Carries a `console_url` to the user's detail page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uid": "<uid>"
    },
    "name": "get_end_user"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the burden. It clearly states what is included (profile fields, spaces, console_url) and what is never included ('Never any conversation content'), which is a strong privacy guarantee. It stops short of addressing error handling or access control, but this is sufficient for a simple get operation.

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 two sentences, front-loaded with the main action, and every sentence adds value: the first identifies the resource and fields, the second adds exclusions and a return value detail. No wasted words.

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 simple one-parameter get tool, the description covers the scope of data returned, privacy constraints, and a notable output field (console_url). The output schema exists to handle return values, so the description is adequately complete for an agent to select and invoke correctly.

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?

The schema provides no description for the single required parameter 'uid', and the description doesn't explicitly define it beyond the context of getting 'end user's detail'. Since 'uid' is a self-explanatory acronym, the description partially compensates, but it doesn't specify format, source, or how to obtain it.

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 starts with 'Get one end user's detail' which is a specific verb+resource pair, and enumerates the exact fields returned (name, contact email/phone, city, timezone) plus their spaces. This distinguishes it from sibling list_end_users, which retrieves multiple users, and from other get_* tools.

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 'one end user' implies this is for a single user detail, contrasting with list_end_users for multiple users. However, it does not explicitly mention alternatives or exclusions, so it's clear but not as directive as naming the alternate tool.

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

All agent4.io 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?