Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — Set Discovery Tips

set_discovery_tips

Configure feature-tip preferences by enabling or disabling tips, switching between guided and expert modes, or snoozing all tips for a set number of days.

Instructions

Adjust the feature-tips preference (the user's control).

Args:
    enabled:     True/False to turn tips on/off entirely.
    power_user:  True = expert mode (tips stay quiet); False = guided mode.
    snooze_days: >0 to snooze ALL tips for N days ("remind me later").

Input Schema

NameRequiredDescriptionDefault
enabledNo
power_userNo
snooze_daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'adjust the feature-tips preference' without describing persistence, side effects, or response behavior. Agent has no insight into what happens after execution.

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?

Extremely concise: a single line for purpose followed by three lines for parameters. Front-loaded with purpose. No unnecessary words; every sentence adds value.

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 preferences tool, parameter descriptions are adequate. However, lacks information about output format or return value (output schema exists but unused), and whether changes take effect immediately or require confirmation.

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

Parameters5/5

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

Schema coverage is 0%, so description is the sole source of parameter meaning. It adds clear, actionable explanations for each parameter: enabled (turn on/off), power_user (expert vs guided mode), snooze_days (snooze for N days). Significantly enhances understanding beyond the schema.

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?

Description clearly states it adjusts the feature-tips preference, using a specific verb ('adjust') and resource ('feature-tips preference'). This distinguishes it from sibling tools like 'next_discovery_tip' (shows tip) and 'discovery_status' (gets status).

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 explicit guidance on when to use this tool versus alternatives. Does not mention prerequisites, exclusions, or when not to use it. Agents must infer usage from the purpose alone.

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