Skip to main content
Glama

whoami

Read-onlyIdempotent

บอกว่าการเชื่อมต่อนี้ยืนยันตัวตนแล้วหรือยัง และเป็นบัญชีใด (user_id + scopes จาก OAuth token) พร้อมอีเมลติดต่อทีมงาน. ใช้เมื่อผู้ใช้ถามว่าเชื่อมบัญชีถูกไหม หรือ tool อื่นตอบเรื่องสิทธิ์/เข้าสู่ระบบแล้วต้องการตรวจ — ไม่ต้องเรียกก่อนใช้ tool อื่น (tool อื่นตรวจสิทธิ์เอง) · โควตาคงเหลือดูจาก quota ในผลของ tool ที่นับโควตา ไม่ใช่ที่นี่ ไม่นับโควตา · อ่านอย่างเดียว · authenticated=False = ยังไม่เชื่อมบัญชี (ยังได้ support_email)

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
scopesNo
user_idNo
authenticatedNo
support_emailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Despite annotations already declaring readOnlyHint/idempotent/destructive=false, the description adds genuinely non-structured behavior: it does not consume quota, and authenticated=False still returns support_email as a fallback. Those are the exact facts an agent needs to interpret a negative result without retrying or escalating.

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 outcome, then usage, then caveats — good ordering and no filler sentences. It loses a point for mild redundancy: 'ไม่นับโควตา' appears both as a quota redirect and again in the trailing characteristics list, and the parenthetical asides make the middle section denser than needed.

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 and the tool has no inputs, so the description only had to cover purpose, routing and the negative-result semantics — all present. Nothing an agent needs in order to call this 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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description instead documents the shape of the response (user_id + scopes), which is useful but sits outside this dimension's scope.

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?

Names a specific verb+resource: reports whether this connection is authenticated and which account, enumerating the returned fields (user_id, OAuth scopes, support_email). No sibling tool in the list touches identity/auth, and the description makes the boundary obvious.

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?

Gives explicit triggers ('when the user asks whether the account connection is correct', or a permission/login error from another tool) and an explicit anti-trigger ('no need to call before using other tools, they check permissions themselves'). It also redirects quota questions to the quota field in counting tools' results, so an agent cannot route that question here by mistake.

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