Skip to main content
Glama
Sign In
packmate-mcp

packmate-mcp

by umbra2728
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_pattern_enabled

Toggle a saved pattern on or off to control detection without removing it from the list.

Instructions

Enable or disable a pattern without deleting it.

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": {
      "pattern_id": "<pattern_id>",
      "enabled": "<enabled>"
    },
    "name": "set_pattern_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
pattern_idYes
enabledYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It states the core effect but does not mention idempotency, side effects (e.g., does it trigger any actions?), or error conditions. It is minimally adequate but lacks depth.

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, front-loaded sentence that conveys the essential purpose without any fluff. Every word earns its place.

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 simple toggle tool, the description combined with the schema and output schema (present) is functional. However, the lack of parameter semantics and usage guidelines means an agent might misunderstand edge cases or fail to use it correctly in sequences.

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?

Schema description coverage is 0%, yet the description does not add any meaning to the parameters (pattern_id, enabled). The agent receives no guidance on what values are valid or how they affect behavior beyond the schema types.

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 clearly states the action (enable/disable) and the resource (pattern), and it distinguishes from the sibling tool 'delete_pattern' by noting 'without deleting it'.

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 implies when to use (versus delete_pattern) but does not provide explicit guidance on when to enable vs. disable, or any prerequisites or alternatives like 'update_pattern' which might also modify pattern state.

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