Skip to main content
Glama

Get Cover Letter Cost

get_cover_letter_cost
Read-onlyIdempotent

Estimate how many credits a cover letter generation would cost for the given inputs. Does not create a cover letter or deduct credits. Prefer list_user_job_listings first so the user can pick a saved job and you pass jobListingId (omit companyName/role/jobPosition). Optionally pass sourceCoverLetterId to include regeneration discounts. Pair with get_user_profile (creditsAmount) to confirm the user can afford generation before create_cover_letter.

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

Input Schema

NameRequiredDescriptionDefault
roleNoJob role / title. Required when jobListingId is not provided.
toneNoCustom tone content (required when toneTemplate is "custom")
filesNoPreviously uploaded files (CV/resume) from list_user_files. Prefer these when present. Optional when personBio holds user-confirmed background from chat.
languageNoISO language code, e.g. "en"en
jobMarketNoJob market index: 0=Europe, 1=NorthAmerica, 2=SouthAndCentralAmerica, 3=MiddleEastAndAfrica, 4=AsiaPacific
keyPointsNoUp to 7 key points to highlight (max 50 chars each)
personBioNoCandidate bio / background. When list_user_files returns no CV/resume, use a bio the user confirmed in chat (they may have edited your draft). Draft from grounded data when available; never invent experience, skills, or education. Prefer uploaded files when available; personBio alone is enough to create without files.
personNameNoCandidate full name
companyNameNoTarget company name. Required when jobListingId is not provided.
jobPositionNoFull job description. Required when jobListingId is not provided.
jobListingIdNoID from list_user_job_listings. When provided, company/role/job description are loaded from the saved listing — omit companyName, role, and jobPosition. Prefer this over manual fields whenever the user has a saved listing.
toneTemplateNoTone template key, e.g. energetic, professional, customenergetic
desiredLengthNoLength scale 0-4 (0=very short, 4=highly elaborate)
personProfessionNoCandidate profession / title
sourceCoverLetterIdNoIf regenerating, ID of the source cover letter (applies regeneration discount when valid)

Output Schema

NameRequiredDescriptionDefault
costNo
kindYes
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / files / maxItems
      Added value: +4
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is structured. The description still adds real value by stating no credits are deducted and that the call is a pure estimate, plus the affordability cross-check against get_user_profile. It stops short of describing pricing variables or failure behavior when inputs are insufficient, which keeps it at 4 rather than 5.

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?

Four sentences, front-loaded with the purpose and the negative scoping before any routing detail. Every clause carries an operational instruction; there is no restatement of the tool name or filler.

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 15-parameter estimator with full schema descriptions and an output schema (so return shape need not be explained), the description supplies exactly what structured fields cannot: the calculation-only guarantee, the preferred input path, and the downstream pairing. Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by consolidating the cross-parameter dependency between jobListingId and the manual companyName/role/jobPosition trio into one rule an agent can act on. It also flags sourceCoverLetterId as the discount lever, adding intent the schema only hints at. It does not explain how tone, desiredLength, or jobMarket influence the estimate.

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 first sentence names a specific verb and resource ('Estimate how many credits a cover letter generation would cost') and immediately scopes it correctly as a read-only calculation. The second sentence explicitly excludes the adjacent operations ('Does not create a cover letter or deduct credits'), separating it cleanly from create_cover_letter and regenerate_cover_letter.

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?

It gives ordered, actionable routing: call list_user_job_listings first so the user picks a saved job, then pass jobListingId and omit companyName/role/jobPosition. It also names sourceCoverLetterId for regeneration discounts and recomputes a pre-flight check via get_user_profile before create_cover_letter, covering when-to-use and how it chains with siblings.

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