Skip to main content
Glama

面灵AI 面试助手

get_job_apply_profile

Read-only

查看用户的网申档案:标准字段(键名、值、来源)与随投递学到的长尾问答(题面归一化键、值、学自哪家)。长尾问答较多时可按关键字筛选。(需要用户授权,范围 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_job_apply_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordNo只列题面或值包含该关键字的长尾问答(选填)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the required authorization scope (job_applications:read) and the shape of the returned data, which an agent cannot infer from annotations alone.

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?

The description is front-loaded with the core purpose and return contents, then the filter hint, then the auth note. It is dense but every clause carries information; the parenthetical auth scope is well placed at the end.

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 read-only tool with one optional parameter and no output schema, the description covers what is returned, how to narrow results, and the authorization requirement. The only minor gap is the absence of explicit sibling routing, but the core call requirements are complete.

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 100%, so the keyword parameter is already documented in the schema. The description still adds value by explaining the intent of the filter (narrowing the long-tail Q&A list when it is large), giving usage context beyond the raw field definition.

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 opens with a specific verb+resource (查看用户的网申档案) and then enumerates exactly what the profile contains: standard fields (key, value, source) and long-tail Q&A learned from submissions (normalized key, value, source company). This clearly separates it from mutating siblings like update_job_apply_profile and delete_job_apply_profile_field.

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?

It gives a concrete condition for the optional keyword filter ('长尾问答较多时可按关键字筛选'), which is useful. However, it never states when to prefer this tool over siblings such as extract_job_apply_profile_from_resume or get_job_apply_client_status, so the routing guidance is only implied by the read-only framing.

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