Skip to main content
Glama

面灵AI 面试助手

get_recruiting_login_phone

Read-only

查看网申 AI 登录 / 注册招聘站使用的手机号:档案中填写的优先,未填写时为面灵账号绑定的手机号。(需要用户授权,范围 job_applications:read)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's real contribution is the data-resolution semantics (profile value takes priority, account-bound number as fallback) and the authorization scope requirement. This is meaningful behavioral context an agent would not get from annotations alone. It does not state what happens when neither source exists, which keeps it below a 5.

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?

A single front-loaded sentence states the resource first, then the resolution precedence, then the authorization requirement. Every clause carries information and nothing is redundant.

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?

With no parameters and no output schema, the description covers what an agent needs: what is returned, how the value is chosen, and that authorization is required. The only gap is the no-data case (neither profile nor account phone present), which leaves the agent guessing at the failure shape.

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 no parameter semantics to explain and the baseline of 4 applies. The schema (empty object, additionalProperties=false) is fully self-describing for a no-arg call.

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 names a specific verb+resource pair (retrieve the phone number used for AI login/registration on the recruiting site) and immediately clarifies the resolution order between two sources. An agent can distinguish this from sibling account/device lookups such as get_login_devices or get_account because the returned value is explicitly the login phone bound to the application profile or account.

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

Usage Guidelines3/5

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

Usage is only implied: the agent learns this is the tool for obtaining the login phone, and the parenthetical states the required authorization scope (job_applications:read). There is no explicit when-to-use vs. when-not guidance, and no named alternative such as update_recruiting_login_phone for changing the value or get_login_devices for device-level info.

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