Skip to main content
Glama
Sign In
workflow-hints

workflow-hints

by PradellaNicolas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

hints_set_preferences

Update local thresholds and notification settings to control when workflow hints trigger, aligning nudges with your work style.

Instructions

Update local hint thresholds and notification settings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hints_set_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
workdays_onlyNo
notify_enabledNo
low_mcp_after_minutesNo
idle_threshold_minutesNo

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the update action but does not explain persistence, whether omitted parameters are reset or preserved, side effects on existing settings, or what the tool returns. For a mutation-like tool this is a notable gap.

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 concise sentence with no redundant wording. It is front-loaded and easy to parse, though it sacrifices parameter-level detail for brevity.

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 four undocumented optional parameters, no output schema, and no annotations, the description is too sparse to fully equip an agent to invoke the tool correctly. It does not clarify update semantics, parameter meanings, or expected return value, so more context is needed.

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?

Schema description coverage is 0% and the description does not explain the individual parameters. It only vaguely groups them under 'hint thresholds and notification settings', which conveys some meaning but leaves the semantics of workdays_only, notify_enabled, low_mcp_after_minutes, and idle_threshold_minutes ambiguous.

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 states a clear action ('Update') and a specific resource ('local hint thresholds and notification settings'), which distinguishes it from sibling tools like hints_record_event or hints_get_context. It could be slightly more explicit about it being a preference-management tool, but the intent is immediately understandable.

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 gives no explicit guidance on when to use this tool versus alternatives, and no mention of prerequisites or exclusions. Usage is only weakly implied by the title and sibling names, so an agent has to infer the appropriate context.

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