Skip to main content
Glama

Metis — Discovery Status

discovery_status

Check whether just-in-time feature tips are on or off, view current mode, active snooze, and adoption count of shown features.

Instructions

Report the discovery-tips state and a simple adoption read.

Tells you whether the just-in-time feature tips are on or off, the current
mode, any active snooze, and how many tips have been shown versus how many
of those features the user has since started using (adoption). Use it to
answer "are tips on?" or to sanity-check before changing them with
set_discovery_tips. Pairs with discovery_intro and next_discovery_tip.

Takes no arguments.

Returns:
    A one-line text summary: on/off, mode, snooze note, shown count, and
    how many shown features are now adopted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, but the description discloses that the tool takes no arguments and returns a text summary describing multiple metrics. It does not explicitly state it is read-only or non-destructive, but the reporting nature implies it. The behavioral summary is adequate.

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 concise (5 sentences), front-loaded with the primary action, and structured logically: purpose, detailed output, usage hints, and no extraneous content.

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

Completeness5/5

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

Despite zero parameters and existing output schema, the description fully covers the tool's purpose, invocation context, and return value format, making it self-contained for an agent to understand and use correctly.

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

Parameters4/5

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

Schema coverage is 100% with no parameters, so the description's statement 'Takes no arguments' adds clarity beyond the schema, achieving the baseline of 4 for no-parameter tools.

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 it reports the discovery-tips state and adoption read, with specific details (on/off, mode, snooze, counts). It distinguishes from siblings by naming them and explaining the tool's role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly suggests use cases ('answer are tips on?', 'sanity-check before changing') and mentions sibling tools for alternative actions (discovery_intro, next_discovery_tip, set_discovery_tips). Provides clear context for when to invoke.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server