Skip to main content
Glama
Sign In
mcpforwork

mcpforwork

by avivancos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

set_active_profile

Switch the active profile to manage job search and application preparation under the desired profile.

Instructions

Switch the active profile.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "set_active_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Switch the active profile.' It does not explain what happens to the previous active profile, whether the change is reversible, persists across sessions, or requires specific permissions. This lack of detail leaves the agent to infer side effects, which is risky for a mutating operation.

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?

The description is a single, short sentence that is easy to parse and front-loads the core action. Every word earns its place, with no redundant phrasing or filler. It is concise in the best sense.

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?

Despite having an output schema, the description omits crucial context about what 'active profile' means, how it relates to other profile tools, and whether there are any constraints or side effects. The description is too sparse to fully guide an agent in a context where many sibling profile-related tools exist.

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

Parameters1/5

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

The input schema has one parameter (profile_id) with no description, and the tool description does not mention any parameters at all. With schema description coverage at 0%, the description fails to provide any meaning for profile_id beyond its type, leaving the agent unsure what value to pass or how it relates to the active profile.

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 description 'Switch the active profile.' uses a specific verb ('switch') and a clear resource ('active profile'), making the tool's purpose immediately understandable. It distinguishes itself from sibling tools like create_profile, get_profile, and set_style_profile by focusing on changing the active profile rather than creating, reading, or styling one.

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?

No guidance is provided about when to use this tool versus alternatives. There is no mention of prerequisites, whether this should be called before other profile-related operations, or any context about what 'active profile' means. The description simply states the action without any usage protocol.

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