Skip to main content
Glama

我是谁 / 默认往哪发

feishu_whoami
Read-only

Returns the bot's identity (open_id, name) and current default chat settings. Call it before sending messages to confirm the target conversation or check whether a target must be specified first.

Instructions

返回机器人身份(open_id、名字)与当前默认会话配置。在发任何消息之前不确定目标会话时,先调这个。如果 default_chat_id 为空,说明必须先指定 target 才能发送。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds real value on top: which identity fields are returned, that a default session config is included, and how to interpret an empty default_chat_id — an interpretation the agent could not derive from annotations or the empty schema.

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?

Three short sentences, each doing distinct work: what is returned, when to call it, and how to read the failure condition. The purpose is front-loaded and there is no filler or repetition.

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?

There is no output schema, so the description must describe the return values — it names open_id, name, and default_chat_id explicitly. For a zero-parameter read-only identity check, nothing an agent needs in order 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 tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it correctly avoids inventing parameter discussion for an argument-free call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it returns the bot identity (open_id, name) plus the current default session configuration. That is concrete enough for an agent to know exactly what it gets back, though it does not name a sibling tool or explicitly contrast itself with the messaging tools it precedes.

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?

It gives a clear precondition — call this first before sending any message when the target chat is uncertain — and a decision rule for the result: an empty default_chat_id means a target must be specified before sending. There is no explicit 'do not use when' clause, but the conditional follow-up covers the practical branch an agent will hit.

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