Skip to main content
Glama

面灵AI 面试助手

get_resume

Read-only

读取一份简历的文本内容。简历 ID 取自 list_resumes。(需要用户授权,范围 resumes:read)

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": {
      "resumeId": "<resumeId>"
    },
    "name": "get_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description's real addition is the authorization requirement and scope 'resumes:read', which is genuinely useful for an agent that may hit permission failures. It says nothing about behavior on missing/inaccessible resumes or on large resumes, so it remains modest.

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 compact sentences: action first, parameter provenance second, permission requirement last. No filler and nothing repeated from the schema or annotations.

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 simple single-parameter read tool with full annotation coverage and no output schema, the description covers what is returned (text content), where the ID comes from, and the auth scope. Only edge-case behavior (nonexistent or unauthorized resume) is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, so the description must compensate. It does partially, explaining that resumeId is obtained from list_resumes, but adds no format, length, or validity semantics beyond the schema's min/max constraints.

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 gives a specific verb and resource in '读取一份简历的文本内容', making clear this returns resume text rather than metadata. It also implicitly separates itself from list_resumes by naming it as the ID source, though it never explicitly contrasts the two.

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 states the prerequisite workflow: the resume ID must come from list_resumes, which tells the agent to enumerate before fetching. It stops short of any explicit when-not-to-use condition or alternative retrieval path.

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