Metis

Overview Schema Source Related Servers Discussions Admin

Metis · Librarian — Export Citations

export_citations

Export library references to a BibTeX file for import into Word, LaTeX/Overleaf, or reference managers. Filter by query, tag, or collection to build cite-while-you-write citations.

Instructions

Export library references as a citation file (BibTeX).

Closes the "no citation-style export" gap: produces a .bib you can import
into Word (via Zotero/Mendeley), LaTeX/Overleaf, or any reference manager,
and use for cite-while-you-write.

Args:
    query: Optional keyword filter over title/authors/journal. Empty = all.
    tag: Optional tag filter (substring match on the tags field).
    collection: Optional collection-name filter.
    fmt: Output format — currently "bibtex" (RIS available via mine_references).
    limit: Max records to export (default 500).

Writes the file to outputs/exports/ and returns its path + a preview.

Input Schema

Name	Required	Default
`fmt`	No	bibtex
`tag`	No
`limit`	No
`query`	No
`collection`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description discloses file output to outputs/exports/, return of path and preview, and all parameter defaults. It does not mention idempotency or side effects, but the behavior is well-covered for a read/export tool.

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 a single paragraph with a clear opening statement followed by a bullet-like list of arguments. Every sentence adds value, and the structure front-loads the purpose.

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 no annotations and 0% schema coverage, the description covers purpose, usage, parameters, output (path + preview), and provides an explicit alternative. It is complete for the tool's complexity, and an output schema exists.

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

Parameters5/5

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

Schema coverage is 0%, yet the description provides detailed explanations for all 5 parameters (query, tag, collection, fmt, limit), including default values and behavior. This fully compensates for the lack of schema descriptions.

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 exports library references as a citation file (BibTeX) and uses specific verbs like 'Export library references as a citation file'. It differentiates from sibling 'mine_references' by noting RIS format is available there.

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

Usage Guidelines4/5

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

The description provides context for use (cite-while-you-write) and explicitly names an alternative tool for RIS format. It does not explicitly state when not to use, but the alternative implies the exclusion.

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

Deploy Server