Skip to main content
Glama

In text citation

in_text_citation
Read-only

Generate APA 7, MLA 9, Chicago author-date, Harvard, or IEEE in-text citations from author/year details, DOI, or ISBN, with optional page numbers and narrative form.

Instructions

The in text citation that goes with a source, with an optional page number and an optional narrative form for a sentence where the author is named. Give authors and year, or a doi or an isbn and the record fills them in. Inputs: authors (family name plus optional given names), year, doi, isbn, page, form (parenthetical or narrative) and style (apa7, mla9, chicago-ad, harvard or ieee). A doi or an isbn cannot be combined with the other one. Example prompt: "Give the APA in text citation for Smith and Jones 2020 on page 14."

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "in_text_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
doiNoA DOI like 10.1038/nature14539, or a doi.org link. The lookup fills in the authors and the year.
formNoparenthetical is the usual brackets, like (Smith & Jones, 2020, p. 14). narrative puts the author in your sentence and keeps the rest in brackets, like Smith and Jones (2020, p. 14).parenthetical
isbnNoA 10 or 13 digit ISBN. Dashes are fine. The lookup fills in the authors and the year.
pageNo
yearNo
styleNoCitation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard and ieee.apa7
authorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / style / description
      Previous value: -"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date)."New value: +"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard and ieee."
  2. First observedv0.1.3

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish readOnlyHint and openWorldHint, and the description adds meaningful behavioral detail: DOI or ISBN lookup fills in authors and year, and DOI and ISBN cannot be combined. It does not cover lookup failure behavior, but the added disclosure is substantive and consistent with the annotations.

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?

The description is front-loaded with the tool's purpose and then packs the key input rules, form/style options, and an example prompt into a short space. The example earns its place, though some input listing slightly repeats schema information.

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?

For a 7-parameter citation tool with no output schema, the description is complete enough: it explains the output type, input modes, supported styles/forms, and the DOI/ISBN constraint. It could say more about invalid identifiers or missing author/year cases, but the core call behavior is covered.

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?

With only 57% schema description coverage, the description meaningfully compensates by explaining authors, year, DOI, ISBN, page, form, and style inputs. It adds the important mutual-exclusion rule for DOI and ISBN and clarifies narrative vs parenthetical form, though page and year formatting details remain sparse.

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?

The description clearly identifies the resource and output: an in-text citation generated from authors/year or DOI/ISBN, with optional page and narrative form. It is specific enough to distinguish this from bibliography generation, but it does not explicitly differentiate itself from sibling tools such as format_citation or cite_from_doi.

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

Usage Guidelines3/5

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

The description gives input guidance and an example prompt, which implies when the tool is useful. However, it does not state when to use this tool instead of siblings like format_citation, cite_from_doi, cite_from_isbn, or format_bibliography, and it provides no explicit exclusions.

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