Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

discovery_intro

Provides a brief orientation highlighting the top 3-5 capabilities for new users. Answers 'what can you do?' on first use.

Instructions

Return the tiny first-run orientation — the 3-5 highest-value capabilities.

Use ONCE for a brand-new user (or when they ask 'what can you do?'). After this,
rely on `next_discovery_tip` for the long tail. No-op (returns '') if the intro was
already given or tips are off.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Describes behavior fully: returns 3-5 capabilities, is a one-time operation, and is a no-op when already given or tips turned off. No annotations provided, so description carries full burden and meets it.

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?

Three sentences, each serving a purpose: definition, usage instructions, edge case. Very concise and front-loaded.

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?

Covers purpose, usage, and edge cases completely. With no parameters, description is sufficient for an agent to 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?

No parameters in input schema (100% coverage), so baseline is 4. Description adds no parameter info since none exist.

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?

Clearly states it returns a first-run orientation with 3-5 capabilities. Distinguishes from sibling tool 'next_discovery_tip' by specifying the scope (first-run vs long tail).

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 says 'use ONCE for a brand-new user or when asked what can you do', and provides alternative tool and edge case (no-op if already given or tips off).

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