Skip to main content
Glama

discovery_status

Report whether discovery tips are on or off, including mode, snooze status, and shown vs adopted counts. Use to verify state before modifying tips.

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
Behavior5/5

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

No annotations provided, but the description fully discloses behavior: it takes no arguments, returns a one-line text summary with specific components. There are no side effects or contradictions.

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 well-structured with a one-line summary followed by detail. It is moderately sized and front-loaded, though could be slightly more concise.

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?

Given the output schema exists, the description adequately explains the return value content and usage context. It covers what the tool does, when to use it, and what it returns.

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?

The tool has 0 parameters, so schema coverage is 100%. The description correctly notes 'Takes no arguments.' Baseline for 0 params is 4.

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 tool reports the discovery-tips state and adoption read, specifying the resource and action. It mentions it pairs with discovery_intro, next_discovery_tip, and set_discovery_tips, distinguishing it from siblings.

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 states when to use: to answer 'are tips on?' or to sanity-check before changing with set_discovery_tips. It also mentions pairing with discovery_intro and next_discovery_tip, providing clear context.

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