Skip to main content
Glama

scite_enrich_item

Get a Scite citation report for one paper: supporting, contrasting, and mentioning citation counts, plus editorial notices. Use to vet a paper's reception before citing.

Instructions

Fetch a Scite.ai citation report for ONE paper: supporting, contrasting, and mentioning citation counts, the total citing-publication count, and any editorial notices (retraction, correction, expression of concern, erratum). Use this to vet a paper's reception before citing it — richer than a bare citation count. Provide EITHER doi OR item_key (not both needed; doi wins if both are passed). If you pass item_key, the tool pulls the DOI from that Zotero item and fails clearly if none is recorded. doi: the DOI string, with or without 'https://doi.org/' prefix — leading prefixes/whitespace are normalized. item_key: 8-character Zotero item key; must have a DOI in metadata or the 'Extra' field to be resolvable. No Scite account or API key required — uses the free public endpoints, so calls can fail transiently: expect 'Could not reach Scite API — try again later' when Scite is slow or unreachable (not a permanent error). For batch enrichment across many items, use scite_enrich_search (search + enrich in one call); for a retraction scan across a collection/tag, use scite_check_retractions. Example: scite_enrich_item(doi='10.1162/tacl_a_00638') or scite_enrich_item(item_key='RTKZQI8E').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doiNo
item_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses key behaviors: no API key needed, free endpoints, transient failures, clear error message. Also explains DOI resolution from item_key. Lacks some detail on potential rate limits but sufficient for a read-only tool.

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?

Well-structured with purpose, usage, parameter details, behavior, alternatives, and examples. Slightly verbose but every sentence serves a purpose.

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 output schema exists, description covers all needed context: purpose, parameters, behavior, error handling, and alternatives. No gaps observed.

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 has 0% description coverage; description compensates fully, explaining EITHER/OR usage, DOI normalization, item_key format and DOI prerequisite. Adds significant value beyond schema.

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?

Clearly states it fetches a Scite.ai citation report for one paper, listing specific data types. Distinguishes from sibling tools by mentioning alternatives for batch enrichment and retraction scans.

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 tells when to use (vet paper before citing) and provides alternatives: scite_enrich_search for batch, scite_check_retractions for retractions. Also explains parameter selection and transient failure handling.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/54yyyu/zotero-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server