Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — List Templates

list_templates

Lists the researcher's own templates stored in Metis—posters, slide decks, letters—so you can find the right one before creating a poster, presentation, or formal document.

Instructions

List the researcher's own templates stored in Metis — posters, slide decks, letters.

Call this before making a poster, a presentation or a formal document. The
templates are kept inside Metis (a private, machine-local folder), so never
ask the researcher where a template is or to attach it: it is already here,
and create_poster / create_presentation / fill_document_template find it by
name or use the right one by default.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that templates are private and machine-local, and that downstream tools find them by name or use defaults; this is useful context. It does not describe ordering or empty-list behavior, but the output schema covers return shape.

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 front-loaded with the core purpose, followed by when-to-use and important local-storage context. Every sentence adds useful information without repetition.

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?

For a no-parameter list tool with an output schema, the description gives enough context to invoke it correctly: what it returns, when to call it, where templates live, and how downstream tools consume them.

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 zero parameters, so the baseline is 4. There are no parameter meanings to clarify beyond the schema, which correctly has an empty object.

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?

States a specific verb and resource: list the researcher's own templates stored in Metis, with concrete examples (posters, slide decks, letters). It is clearly distinguishable from downstream creation tools like create_poster and create_presentation.

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 to call it before making a poster, presentation, or formal document. It also clarifies that templates are already local and should not be requested from the researcher, which is a strong usage-boundary instruction.

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