Skip to main content
Glama
G-Hensley
by G-Hensley

Get Resume

get_resume

Fetch your resume as markdown. Select a specific variant such as full-stack-react or frontend-react to match a job target.

Instructions

Get the full resume in markdown format, or a specific generated resume variant

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
variantNoResume variant (e.g., 'full-stack-react', 'frontend-react', 'nextjs-focused', 'general-swe'). Leave empty for base resume.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes

Implementation Reference

  • The handler function for the 'get_resume' tool. It reads the base resume (profile/resume.md) or a variant-specific resume using a manifest lookup, and returns the markdown content.
    async ({ variant }) => {
      let resumePath = "profile/resume.md";
      if (variant) {
        try {
          const manifest = await readJsonFile<ResumeManifest>("profile/resumes/latest-manifest.json");
          const found = manifest.resumes.find(r => r.cluster === variant);
          if (found) {
            resumePath = `profile/resumes/${found.file}`;
          }
        } catch {
          // No manifest, fall back to base resume
        }
      }
      const resume = await readMarkdownFile(resumePath);
      return { content: [{ type: "text", text: resume }] };
    }
  • Input schema for the 'get_resume' tool. Defines an optional 'variant' string parameter. Output schema is textContentOutputSchema (text-only content array).
    {
      title: "Get Resume",
      description: "Get the full resume in markdown format, or a specific generated resume variant",
      inputSchema: {
        variant: z.string().optional().describe("Resume variant (e.g., 'full-stack-react', 'frontend-react', 'nextjs-focused', 'general-swe'). Leave empty for base resume."),
      },
      outputSchema: textContentOutputSchema,
    },
  • api/mcp.ts:218-245 (registration)
    Registration of the 'get_resume' tool on the MCP server via server.registerTool() with the name 'get_resume'.
    // Tool: Get Resume
    server.registerTool(
      "get_resume",
      {
        title: "Get Resume",
        description: "Get the full resume in markdown format, or a specific generated resume variant",
        inputSchema: {
          variant: z.string().optional().describe("Resume variant (e.g., 'full-stack-react', 'frontend-react', 'nextjs-focused', 'general-swe'). Leave empty for base resume."),
        },
        outputSchema: textContentOutputSchema,
      },
      async ({ variant }) => {
        let resumePath = "profile/resume.md";
        if (variant) {
          try {
            const manifest = await readJsonFile<ResumeManifest>("profile/resumes/latest-manifest.json");
            const found = manifest.resumes.find(r => r.cluster === variant);
            if (found) {
              resumePath = `profile/resumes/${found.file}`;
            }
          } catch {
            // No manifest, fall back to base resume
          }
        }
        const resume = await readMarkdownFile(resumePath);
        return { content: [{ type: "text", text: resume }] };
      }
    );
  • The textContentOutputSchema used as the output schema for get_resume and other tools.
    const textContentOutputSchema = z.object({
      content: z.array(
        z.object({
          type: z.literal("text"),
          text: z.string(),
        })
      ),
    });
  • Helper function readMarkdownFile used by the handler to fetch markdown resume content from GitHub.
    async function readMarkdownFile(relativePath: string): Promise<string> {
      return fetchFromGitHub(relativePath);
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It states the action (get) and output format (markdown), implying a read operation, but does not explicitly confirm there are no side effects or rate limits. Adequate but not highly transparent for a simple retrieval tool.

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?

Single sentence, 13 words, efficiently conveys the core action and parameter nuance. Could benefit from slightly more structure (e.g., listing variants) but remains concise and front-loaded.

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 existence of an output schema, the description need not detail return values. It covers the main use case and mentions markdown format. However, lacking annotations, it could be enhanced by explicitly stating it's read-only or listing available variants more thoroughly.

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 100% coverage, but the description adds meaningful context: 'Leave empty for base resume.' This clarifies behavior beyond the schema's description, aiding correct invocation.

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 clearly states the tool retrieves a resume in markdown format, either the base version or a specific variant. It effectively differentiates itself from sibling 'get_' tools by specifying the resource (resume) and the format.

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?

No guidance on when to use this tool versus alternatives like other get tools. Does not mention when to specify a variant versus leaving it empty beyond a brief note in the parameter description. Missing context about prerequisites or exclusions.

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/G-Hensley/myself-mcp-server'

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