Skip to main content
Glama

get_cover_letter

Read-only

Read one stored cover letter by id. Returns the letter, its S3 version (ETag), and an appUrl the user can open.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coverLetterId": "<coverLetterId>"
    },
    "name": "get_cover_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
coverLetterIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds real value by disclosing what comes back—the letter, its S3 version/ETag, and an appUrl—which matters because there is no output schema. It does not say what happens when the id does not exist, keeping it below a 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?

Two short sentences: the operation is front-loaded and the second sentence covers return payload. Every clause carries information and 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?

For a simple single-record read, the description covers both the action and the return shape, which is the main gap left by the absent output schema. The remaining omission—behavior on a missing or invalid id—is minor but real.

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

Parameters3/5

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

With a single parameter at 0% schema description coverage, the schema contributes nothing beyond the name coverLetterId being a string. The description only says "by id," adding no format, source, or constraint information, so compensation for the coverage gap is minimal.

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?

"Read one stored cover letter by id" gives a specific verb (read), resource (cover letter), and cardinality (one), which distinguishes it from list_cover_letters and the create/update/delete siblings. It stops short of naming an alternative explicitly, but the single-record scope is unambiguous.

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: the agent can infer this is the way to fetch a single letter once it has an id. There is no statement about when to use this versus list_cover_letters or what to do if the id is unknown or stale.

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