Skip to main content
Glama

List Matchaa resume designs

list_resume_templates
Read-only

Use this when you need to pick or change the resume design: lists the 19 Matchaa templates, what each suits and the valid palette, font and spacing values, as text. Choose the template yourself from the profile, the amount of content and the preferences already stated; do not ask the user unless they want to choose. Photo templates need a photo the user already provided. Do not use to apply a design to a delivered resume; use update_resume with templateId.

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

Input Schema

NameRequiredDescriptionDefault
languageNofr
includePreviewsNo

Output Schema

NameRequiredDescriptionDefault
templatesYes
defaultTemplateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world, so the safety profile is covered; the description adds real context on top: the fixed count of 19 templates, that output is textual rather than rendered, that the returned catalog includes valid palette/font/spacing values, and a precondition for photo templates. It stops short of describing pagination or the payload structure, but an output schema exists to cover that.

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?

Front-loaded with the 'Use this when' trigger, then payload, then decision guidance, then the exclusion — a sensible order with no filler sentences. The first sentence is long and comma-heavy, packing payload details into a single clause, but every element earns its place.

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

Completeness5/5

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

For a read-only catalog tool with an output schema, an agent needs selection policy, preconditions, and routing to the mutating sibling — all three are present, and the return payload is described in outline so the schema can handle structure. The only gap, undocumented parameters, is minor for defaults-only arguments.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description carries the full burden and does not meet it: neither 'language' (fr/en, default fr) nor 'includePreviews' is mentioned or explained. The phrase 'as text' hints at preview-free output but never clarifies what includePreviews toggles or what language affects.

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?

States a specific verb and resource ('lists the 19 Matchaa templates') plus the exact payload (what each suits, valid palette/font/spacing values, as text). It also names the sibling it is not ('use update_resume with templateId'), so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Gives the trigger ('when you need to pick or change the resume design'), an explicit exclusion ('Do not use to apply a design to a delivered resume') with the named alternative, and even decision policy: choose from the profile yourself, only ask the user if they want to choose, and skip photo templates unless the user already supplied a photo.

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