Skip to main content
Glama
Sign In
DrawOffer MCP Server

DrawOffer MCP Server

by ql-link
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

列出简历

list_resumes
Read-only

Lists all resumes in the current DrawOffer account, including ID, title, default status, and update time, sorted by update time.

Instructions

列出当前 DrawOffer 账号里的全部简历（ID、标题、是否默认简历、更新时间），按最近更新排序。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real context beyond them: results are scoped to the current account, contain no cross-workspace results, and are sorted by most-recent update. It does not discuss pagination or result-size limits, which is the main remaining gap.

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?

One sentence, front-loaded with the verb and scope, then the returned fields, then the ordering. Every clause carries information an agent needs; 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 output schema, the description carries the burden of describing returns and does so (ID, title, default flag, update time) plus ordering. Only the absence of any note on result size or truncation for accounts with many resumes keeps it short of full completeness.

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 nothing for the description to disambiguate. Baseline 4 applies; the description correctly signals a parameterless call by framing the scope as the whole account.

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 (简历) plus scope (当前 DrawOffer 账号里的全部). It also names the returned fields and sort order. It does not explicitly name the sibling get_resume as the single-item alternative, so differentiation is implied by '全部' rather than stated.

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: an agent can infer this is the tool for enumerating all resumes, but there is no explicit when-to-use/when-not guidance and no sibling such as get_resume is named as the alternative for a single record.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools