Skip to main content
Glama

next_discovery_tip

Shows one relevant, undiscovered feature tip based on user's current activity, without repeating past tips.

Instructions

Return ONE earned, not-yet-shown feature tip for the current moment (or '').

Call at natural trigger moments (user starts a project, writes R code, builds a
library, asks a knowledge question, handles a dataset…). Pass `context` as
comma-separated trigger tags. Returns at most one tip — and ONLY for a feature the
user does NOT already use (earned discovery), respecting the off/snooze/power-user
settings and a frequency cap (≤1 tip / 20 min, ≤3 / day). Records it so it never
repeats. Returns '' when nothing should be shown. Weave the tip in naturally.

Args:
    context: comma-separated trigger tags describing what the user is doing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNo

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 description fully discloses behavior: respects off/snooze/power-user settings, frequency cap (≤1/20min, ≤3/day), records to avoid repeats, returns empty string when inappropriate.

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?

Description is front-loaded with core purpose and well-structured with paragraphs. Slightly verbose but each sentence adds value.

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 tool complexity (frequency caps, user settings) and presence of output schema (not shown but indicated), description covers all necessary context for correct invocation.

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 0%, but description adds meaning: 'comma-separated trigger tags describing what the user is doing' for the context parameter.

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 returns one earned, not-yet-shown feature tip (or empty string). Distinct from siblings which are mostly CRUD or search tools.

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?

Provides explicit trigger moments (user starts project, writes R code, etc.) and explains when not to call (if user already uses feature, frequency cap, returns empty).

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_PH'

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