Skip to main content
Glama
Sign In
career-mcp

career-mcp

by sindhujaIBM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

save_voice_profile

Stores a description of your writing voice and tone so generated cover letters and LinkedIn About sections sound like you, not generic AI copy.

Instructions

Store a description of the user's writing voice/tone (e.g. tone attributes, phrases to avoid, sample posts). Used to keep generated cover letters and LinkedIn About sections sounding like the user, not generic AI copy.

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": {
      "voice_text": "<voice_text>"
    },
    "name": "save_voice_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
voice_textYesDescription of tone, style, and things to avoid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
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 behavioral burden for a write operation. It never discloses whether an existing voice profile is overwritten, whether prior content is lost, what permissions or auth are required, or what the call returns; 'Store' alone leaves the mutation semantics ambiguous.

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?

Two sentences, front-loaded with the core action and parenthetical examples kept tight. The second sentence is purpose framing rather than specification, but it earns its place by explaining why the stored text matters.

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?

For a single required string parameter with no output schema, the description covers purpose and content guidance adequately. Given that annotations are absent, it should also address the overwrite/replace behavior of a 'save' tool and its relationship to get_voice_profile to be fully complete.

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, but the description adds genuine meaning by enumerating content categories (tone attributes, phrases to avoid, sample posts) that go beyond the schema's terse 'Description of tone, style, and things to avoid', helping the agent compose a good voice_text.

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?

States a specific verb and resource: 'Store a description of the user's writing voice/tone', with concrete examples of what that content looks like (tone attributes, phrases to avoid, sample posts). The distinction from the sibling get_voice_profile is only inferable from the save_/get_ naming pair, not stated in the text.

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?

The description gives downstream purpose ('keep generated cover letters and LinkedIn About sections sounding like the user'), which implies when the content is useful. It does not say when to call this tool versus get_voice_profile, nor whether it replaces or appends to an existing profile, leaving usage to inference.

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

Deploy Server

Other Tools