Skip to main content
Glama

面灵AI 面试助手

update_recruiting_login_phone

修改网申 AI 登录 / 注册招聘站使用的手机号;传空字符串清除,之后改用面灵账号绑定的手机号。回包为读回后实际生效的号码。(需要用户授权,范围 job_applications:write)

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": {
      "mobile": "<mobile>"
    },
    "name": "update_recruiting_login_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
mobileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say readOnly=false, destructive=false, openWorld=false; the description adds the material context that isn't there: it requires user authorization with scope job_applications:write, empty input triggers a fallback to the account-bound number, and the response echoes the value actually persisted after read-back. It doesn't cover whether the change invalidates existing sessions or needs re-login, which is the remaining behavioral gap for a credential-adjacent mutation.

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 tight clauses, front-loaded with the action, then the clearing rule, then the return-value contract and auth note. No filler, and the most easily-misused detail (empty string) is called out before the authorization aside.

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 one-parameter mutation with no output schema, it covers purpose, the empty-string edge case, the authorization requirement, and what the response reflects. The only missing piece an agent would want is the phone-number format expectation.

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?

Schema coverage is 0% for the single `mobile` string, so the description carries the burden and does explain the non-obvious sentinel semantics (empty string = clear, not an invalid value). It still leaves the expected format ambiguous (international prefix, digits-only vs formatted) for a field that permits up to 32 characters.

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 (修改) plus the exact resource: the phone number used by the recruiting-site AI login/registration flow. This makes it plainly distinct from the read-side sibling get_recruiting_login_phone without needing to name it.

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?

Explains the operative case (set a new number) and the special case (empty string clears it, falling back to the 面灵 account-bound number), plus the authorization prerequisite and scope. It does not explicitly say when not to use it or point at alternatives, so it stops short of a 5.

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