Skip to main content
Glama
mikenguyen13

Research Methods Library

by mikenguyen13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Format references

cite
Read-onlyIdempotent

Format references in APA, Chicago, MLA, Harvard, BibTeX, or RIS. Pass section or source IDs to get a deduplicated citation list, or omit IDs to cite all works.

Instructions

Format references for works in the library in APA, Chicago, MLA, Harvard, BibTeX, or RIS. Pass the ids of the sections you used to get a deduplicated reference list plus the section links, or pass source ids to cite whole works. With no ids, returns a reference for every work in the library.

Input Schema

NameRequiredDescriptionDefault
idsNoSection ids, or source ids: data_analysis, causalverse, credit_score, marketing_research, ai_in_action, advanced_data_analysis, tidy_finance_vn, tidy_finance_vn_vi, mlpy, publications.
styleNoCitation style (default apa).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / ids / description
      Previous value: -"Section ids from other tools, or source ids: data_analysis, causalverse, credit_score, marketing_research, ai_in_action."New value: +"Section ids, or source ids: data_analysis, causalverse, credit_score, marketing_research, ai_in_action, advanced_data_analysis, tidy_finance_vn, tidy_finance_vn_vi, mlpy, publications."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavior: deduplication of overlapping section citations, inclusion of section links, and the default all-works behavior when ids are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action and supported styles, followed by the id semantics and the no-id fallback. Every sentence carries information, though the middle sentence is dense enough to require a second read.

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?

With no output schema, the description still conveys what comes back (a reference list, deduplicated, with section links, or one reference per work). Combined with the fully documented two-parameter schema, an agent has everything needed to invoke it correctly.

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 meaning the schema lacks: it explains that "ids" can be either section ids (yielding deduped references plus links) or source ids (citing whole works). It also confirms the default style when none is passed, which the schema only parenthetically notes.

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 a specific verb and resource ("Format references for works in the library") and enumerates the supported styles, so an agent knows exactly what it produces. It does not explicitly differentiate itself from siblings like list_sources or search, 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 Guidelines4/5

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

Clearly lays out the three invocation modes: pass section ids to get a deduplicated list plus links, pass source ids to cite whole works, or pass nothing to get every work. It gives strong context for each mode but names no exclusions or alternative tools for related needs.

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