Skip to main content
Glama

Zotero Search By Citation Key

zotero_search_by_citation_key

Finds the one Zotero item matching an exact, case-sensitive BetterBibTeX citation key by checking the citationKey field and Citation Key lines in Extra; use item search for partial keys or free text.

Instructions

Find the one item with this BetterBibTeX citation key (exact, case-sensitive), e.g. 'smith2024'. Checks Zotero's citationKey field, then 'Citation Key:' lines in Extra. For partial keys or free text use zotero_search_items.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "citekey": "<citekey>"
    },
    "name": "zotero_search_by_citation_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
citekeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does disclose the lookup order (citationKey field first, then 'Citation Key:' lines in Extra) and that it returns exactly one item. It does not say what happens when no match exists or whether multiple matches are possible, which leaves a real gap for a tool with zero annotation coverage.

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?

Two tight sentences: the qualified purpose first, then the fallback routing. The example is embedded inline rather than wasting a separate clause, and nothing is redundant.

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?

Adequate for a one-parameter read tool with no output schema: the matching semantics and lookup path are explained, and "the one item" sets the return expectation. Only the not-found / empty-result behavior is unstated.

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%, so the description must carry meaning, and it does: it identifies the parameter as a BetterBibTeX citation key, specifies exact and case-sensitive semantics, and supplies a concrete example format ('smith2024'). This is everything needed to construct a valid call.

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 ("Find the one item with this BetterBibTeX citation key") plus the exact matching rule, and explicitly contrasts with zotero_search_items for partial keys. An agent can distinguish it from the search siblings without opening any schema.

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?

Gives the precise condition that selects this tool (exact, case-sensitive BetterBibTeX key, e.g. 'smith2024') and names the alternative for the other case ("For partial keys or free text use zotero_search_items"). Both when-to-use and when-not-to-use are covered.

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