Skip to main content
Glama

面灵AI 面试助手

get_job_intent

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_job_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds value beyond them by disclosing the authorization requirement and the required OAuth scope job_applications:read, which an agent needs to know before calling, and by listing the categories of stored data returned.

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?

A single compact sentence front-loads the resource, then enumerates fields, with the authorization/scope caveat parenthesized at the end. The field enumeration is long but earns its place because there is no output schema to document the return shape. No redundant or filler wording.

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 zero-parameter read with no output schema, the description does the necessary extra work by enumerating what the response contains and stating the permission scope. The only gap is the lack of explicit routing to update_job_intent, which would make the round-trip workflow fully clear.

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 and the schema is an empty closed object at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies since no parameter meaning is missing.

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 pairs a specific verb ('查看' / view) with a specific resource (the AI-remembered job intent) and enumerates its contents: target companies, excluded companies, company size, direction, recruitment type, city, batch. An agent can immediately tell this is a read of stored preferences rather than an application record. It does not explicitly name update_job_intent as the mutation counterpart, so it stops short of full sibling differentiation.

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 implied rather than stated: an agent infers it should read the stored intent before applying or updating it, and the '(需要用户授权,范围 job_applications:read)' note gives a real prerequisite. However, there is no explicit when-to-use/when-not-to-use guidance and no named alternative (e.g., 'to change these values, use update_job_intent').

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