Skip to main content
Glama
Sign In
trahloff

Aldine

by trahloff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List citation keys

list_citations
Read-only

Lists citation keys from a project's .bib files with title, author, year, and file so you can call it before writing a \cite and avoid inventing keys; missing keys should be added or requested.

Instructions

Citation keys defined in the project's .bib files: [{key, title, author, year, file}]. Always call it before writing a \cite — never invent a key. A key you need that is missing: add it with references_add, or ask the user.

Input Schema

NameRequiredDescriptionDefault
branchNoBranch name (defaults to 'main'). Every result, error results included, echoes {branch, head} — head is the branch's current commit (after a write, the commit that write made). Pass the branch explicitly whenever you are not on main.
projectNoProject id. Optional when the access token is scoped to exactly one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely useful context: the shape of each returned record and the workflow rule against fabricating keys. It does not discuss cost, ordering, or behavior on empty .bib files, which keeps it from a 5.

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 short sentences: return shape first, then the mandatory-call rule, then the missing-key remedy. No filler, and nothing important is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by spelling out the record fields an agent will receive. Combined with rich parameter documentation, an agent has enough to call it correctly; only edge cases such as an empty or missing .bib file go unaddressed.

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

Parameters3/5

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

Schema description coverage is 100%, so both `branch` and `project` are fully documented in the schema, including the branch/head echo behavior. The description adds nothing about either parameter beyond the incidental phrase 'the project's .bib files', so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource precisely (citation keys defined in the project's .bib files) and even lists the returned fields, which lets an agent distinguish it from siblings like references_add or read_file. The verb is only implicit via the tool name rather than stated in the description, so it falls just short of a 5.

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 instructs when to call ('Always call it before writing a \cite') and states a prohibition ('never invent a key'), then names the alternative path for missing keys: references_add or ask the user. That is exactly the when/when-not/alternative triad.

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