Skip to main content
Glama

get_templates

Retrieve available resume templates with details like ID, name, and thumbnails to help users select appropriate resume styles for NovaCV resume services.

Instructions

获取所有可用的简历模板,返回模板列表及其详细信息,包括模板ID、名称、缩略图等。帮助用户选择最适合的简历风格。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_templates' MCP tool. It calls novaCVService.getTemplates(), stringifies the result, and returns it in the expected MCP response format. Handles errors by returning an error message.
    async (_, extra) => {
      try {
        const templates = await novaCVService.getTemplates();
        return {
          content: [
            {
              type: "text",
              text: safeStringify(templates)
            }
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text",
              text: `错误: ${error.message || "未知错误"}`
            }
          ],
        };
      }
    }
  • src/index.ts:201-227 (registration)
    Registers the 'get_templates' tool on the MCP server using server.tool(). Specifies the tool name, Chinese description, empty input schema ({}), and the handler function.
    server.tool(
      "get_templates",
      "获取所有可用的简历模板,返回模板列表及其详细信息,包括模板ID、名称、缩略图等。帮助用户选择最适合的简历风格。",
      {},
      async (_, extra) => {
        try {
          const templates = await novaCVService.getTemplates();
          return {
            content: [
              {
                type: "text",
                text: safeStringify(templates)
              }
            ],
          };
        } catch (error: any) {
          return {
            content: [
              {
                type: "text",
                text: `错误: ${error.message || "未知错误"}`
              }
            ],
          };
        }
      }
    );
  • NovaCVService.getTemplates() method: Fetches all available resume templates from the NovaCV API endpoint '/api/v1/templates' and returns the response data. Handles errors internally.
    async getTemplates(): Promise<any> {
      try {
        const response = await this.client.get('/api/v1/templates');
        return response.data;
      } catch (error) {
        this._handleError(error);
        throw error;
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It describes the tool as a read operation ('获取' - get) and lists return details, but lacks behavioral context such as whether it requires authentication, has rate limits, returns paginated results, or handles errors. This is inadequate for a tool with zero annotation coverage.

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 concise and front-loaded, stating the core purpose in the first clause. Both sentences add value: the first defines the action and outputs, and the second explains the user benefit. There is no wasted text, though it could be slightly more structured for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and outputs but lacks behavioral details like error handling or performance characteristics. For a read-only tool with no complex schema, this is acceptable but leaves gaps in transparency.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and outputs. This meets the baseline for tools with no parameters.

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 clearly states the tool's purpose: '获取所有可用的简历模板' (get all available resume templates) with specific outputs like template ID, name, and thumbnail. It distinguishes from siblings by focusing on template retrieval rather than analysis, conversion, or generation. However, it doesn't explicitly differentiate from potential similar tools beyond the given siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions '帮助用户选择最适合的简历风格' (help users choose the most suitable resume style), which implies a context of template selection, but offers no explicit when/when-not rules or comparisons to sibling tools like analyze_resume_text or generate_resume_from_text.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HireTechUpUp/mcp-server-novacv'

If you have feedback or need assistance with the MCP directory API, please join our Discord server