Zoteus

Resolve CSL citation styles

zotero_styles

Read-only

Resolve human citation-style names to valid CSL style IDs and verify availability for bibliography formatting. List built-in aliases to find the correct style identifier.

Instructions

Resolve a human citation-style name to a valid CSL style id and confirm it is available, or list common style aliases. action: "resolve" maps names like "APA 7th", "IEEE", "Vancouver", "Chicago", "MLA", "Nature" to the correct CSL id (e.g. apa, ieee, modern-language-association) and verifies the style can be fetched; pass the returned styleId as the style argument to zotero_format_bibliography or zotero_bibliography. action: "list" returns the built-in common aliases (any id from the CSL styles repository also works). Dependent styles are resolved to their independent parent automatically when formatting.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Style name to resolve (e.g. "APA 7th").
`action`	Yes	What to do: "resolve" maps `name` to a CSL style id and checks it can be fetched; "list" returns the built-in common aliases.

Output Schema

TableJSON Schema

Name	Required	Description
`input`	No	The name that was resolved, echoed back.
`common`	No	action:"list": the built-in style aliases. Any id from the CSL styles repository also works.
`styleId`	No	The CSL style id it maps to, e.g. "apa"; pass it as `style` to the bibliography tools.
`available`	No	Whether that style could actually be fetched.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.20.2Sep 16, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed2 schema fields changedv1.20.0Sep 13, 2026

addedInput schema / properties / action / description

Added value: +"What to do: \"resolve\" maps `name` to a CSL style id and checks it can be fetched; \"list\" returns the built-in common aliases."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "available": {
+      "description": "Whether that style could actually be fetched.",
+      "type": "boolean"
+    },
+    "common": {
+      "description": "action:\"list\": the built-in style aliases. Any id from the CSL styles repository also works.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "input": {
+      "description": "The name that was resolved, echoed back.",
+      "type": "string"
+    },
+    "styleId": {
+      "description": "The CSL style id it maps to, e.g. \"apa\"; pass it as `style` to the bibliography tools.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv1.0.4Jul 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description reveals that resolution includes verifying the style can be fetched and that dependent styles are automatically resolved to their independent parents. These are useful behavioral details that an agent would not know from annotations or the schema, and they help set correct expectations about side effects and output.

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 dense paragraph that front-loads the core purpose, then separates the two actions clearly, gives examples, and closes with an integration note. Every sentence contributes meaningful information; there is no filler or redundancy.

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 the presence of a full input schema, an output schema, and annotations, the description completes the picture with usage context, action semantics, integration targets, examples, and edge-case behavior (dependent styles). Nothing needed for correct invocation is missing.

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 is 100%, so the baseline is 3, but the description adds value by providing concrete style-name examples ('APA 7th', 'IEEE', 'Vancouver') and explaining the relationship between the resolved styleId and the style parameter of sibling tools. This goes beyond the raw schema and helps the agent understand how to chain the output.

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 states a precise purpose: resolving a human-readable citation style name to a valid CSL style id and verifying availability, or listing common aliases. It uses concrete verbs ('resolve', 'list', 'maps', 'verifies') and differentiates itself from sibling formatting tools by clarifying its role as the style-resolution step before zotero_format_bibliography or zotero_bibliography.

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?

The description explicitly tells the agent when to use this tool: before formatting, by passing the returned styleId to zotero_format_bibliography or zotero_bibliography. It also provides an alternative ('any id from the CSL styles repository also works') and clarifies the list action use case, leaving no ambiguity about when to invoke which action.

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