Skip to main content
Glama

我的资料

gwl_get_me
Read-onlyIdempotent

Retrieve the profile of the user who owns the current API key, including ID, username, display name, email, avatar, theme, and visibility settings; secrets and permission levels are excluded.

Instructions

读取当前 API Key 所属用户的个人资料(与前端「个人中心」同源)。 返回 id、username、nickname、display_name、email、phone、avatar、theme、introduction、gender、location、group_id/group_name、slug、is_public、workspace_layout 等。 出于安全,永远不含 account_apikey、password_hash、pin;要拿权限等级请用 gwl_get_permissions。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered structurally; the description adds real value on top by guaranteeing sensitive fields (account_apikey, password_hash, pin) are never returned and noting the data source matches the frontend profile center. It doesn't discuss caching or freshness, but nothing here is misleading.

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?

Three short lines, front-loaded with purpose, then return fields, then the security exclusion and the sibling pointer. The field enumeration overlaps with the existing output schema, making it slightly redundant, but it is compact and each remaining sentence carries information.

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 parameterless read with an output schema and full annotations, the description covers purpose, data source, field scope, and the security exclusion — enough for an agent to call it confidently. The only gap is that the long return-field list duplicates the output schema rather than adding constraints on it.

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; the baseline of 4 applies. The description correctly implies no arguments are needed by framing the target as implicit in the API key.

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 ('读取当前 API Key 所属用户的个人资料') and pins the scope to the calling credential, which distinguishes it from the many list/get siblings that take explicit ids. It also names the field set returned, so an agent knows this is the self-profile tool rather than a directory lookup.

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?

Explicitly routes one adjacent need elsewhere: '要拿权限等级请用 gwl_get_permissions', which is the main confusion risk for a profile endpoint. It gives no explicit when-not guidance beyond that and doesn't say what to call for other users' profiles, but the 'current API Key' scoping makes the intended use clear.

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