Skip to main content
Glama
Sign In
mcpforwork

mcpforwork

by avivancos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

set_style_profile

Provide a writing sample to capture your style, ensuring drafts in job search workflows match your voice.

Instructions

Capture the user's writing voice so drafts sound like them.

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": {
      "writing_sample": "<writing_sample>"
    },
    "name": "set_style_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
directivesNo
profile_idNo
writing_sampleYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits itself. It does not explain whether this tool creates a new profile, updates an existing one, overwrites data, or requires specific input formats. The statement only gives an intended outcome, not operational behavior.

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?

The description is a single, front-loaded sentence with no wasted words, effectively communicating the core purpose. However, it is arguably too terse given the need for more explanatory detail.

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

Completeness2/5

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

Given that the tool has three parameters, no annotations, and a minimal description, it is incomplete for safe invocation. Missing information includes side effects, when to use, and parameter semantics, leaving significant gaps.

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?

The schema has 0% description coverage, so the description must compensate. It only vaguely implies a writing sample is involved but does not clarify the roles of directives or profile_id, nor any constraints on writing_sample. This leaves the agent with insufficient parameter understanding.

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?

The description uses the specific verb 'Capture' with the resource 'user's writing voice', conveying the tool's core purpose. However, it doesn't explicitly mention that it sets a style profile or differentiate from sibling tools like create_profile or update_profile.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusion scenarios. It solely states the purpose without contextual usage direction.

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