Skip to main content
Glama
Sign In
NASA SciX MCP Server

NASA SciX MCP Server

by adsabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export

Read-only

Generate citations in 23 bibliographic styles (BibTeX, AASTeX, EndNote, etc.) with custom templates for academic writing and reference management.

Instructions

Export citations in 23 bibliographic formats (BibTeX, AASTeX, EndNote, IEEE, MNRAS, etc.) with support for custom formatting templates.

Input Schema

NameRequiredDescriptionDefault
sortNoOptional sort order (e.g., "date desc")
formatYesExport format
bibcodesYesList of bibcodes to export
keyformatNoCitation key format
maxauthorNoMaximum authors to show before et al.
authorcutoffNoAuthor cutoff threshold
custom_formatNoCustom format string (required when format is custom)
journalformatNoJournal format style code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changedv1.3.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / authorcutoff / anyOf
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "items": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / authorcutoff / description
      Previous value: -"Number of authors before using \"et al.\""New value: +"Author cutoff threshold"
    • removedInput schema / properties / authorcutoff / type
      Removed value: -"number"
    • changedInput schema / properties / bibcodes / description
      Previous value: -"List of SciX bibcodes to export (1-2000)"New value: +"List of bibcodes to export"
    • addedInput schema / properties / bibcodes / maxItems
      Added value: +2000
    • addedInput schema / properties / bibcodes / minItems
      Added value: +1
    • changedInput schema / properties / custom_format / description
      Previous value: -"Custom format string using field specifiers (required when format is custom)"New value: +"Custom format string (required when format is custom)"
    • addedInput schema / properties / journalformat / anyOf
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "items": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / journalformat / description
      Previous value: -"Journal name format: 1 (AASTeX macros), 2 (abbreviations), 3 (full names)"New value: +"Journal format style code"
    • removedInput schema / properties / journalformat / type
      Removed value: -"number"
    • addedInput schema / properties / keyformat / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / keyformat / description
      Previous value: -"BibTeX key format template (e.g., \"%1H%Y\" for FirstAuthorYear)"New value: +"Citation key format"
    • removedInput schema / properties / keyformat / type
      Removed value: -"string"
    • addedInput schema / properties / maxauthor / anyOf
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "items": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / maxauthor / description
      Previous value: -"Maximum number of authors to display (default: 200)"New value: +"Maximum authors to show before et al."
    • removedInput schema / properties / maxauthor / type
      Removed value: -"number"
    • addedInput schema / properties / sort / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order for bibcodes (e.g., \"date desc\", \"first_author asc\")"New value: +"Optional sort order (e.g., \"date desc\")"
    • removedInput schema / properties / sort / type
      Removed value: -"string"
  2. First observedv1.0.14

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, openWorld=true and idempotentHint=false, covering the safety profile. The description adds that custom templates are supported, which is useful context, but omits practical traits like the 2000-bibcode cap and behavior of the 'custom' format path.

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?

A single front-loaded sentence that names the action, the resource, and the breadth of formats without filler. Efficient, though it could have traded a few format examples for usage context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters, 100% schema coverage, and no output schema, the description covers the core capability but says nothing about what is returned (raw text vs structured) or the custom_format requirement, leaving some gaps for an agent to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so every parameter is already documented in structured form. The description reinforces the format dimension and custom-template concept but adds no syntax or semantics beyond what the schema/enum provides, so the baseline 3 applies.

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 (Export) and resource (citations) plus the breadth of output formats. An agent can see this is the citation-formatting tool, distinct from data-retrieval siblings like get_citations or get_references, though the description never explicitly contrasts with them.

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?

Usage is only implied by the word 'export' and the format enumeration; there is no explicit guidance on when to choose this over retrieving citations directly, nor any noted preconditions such as obtaining bibcodes first.

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