Skip to main content
Glama
science-ai-mcp-server

science-ai-mcp-server

by SelfPy

Pre-Check Paper

pre_check_paper

Estimate Tier 1-3 acceptance probabilities and research field from a paper's title and abstract before submission, with evidence strength to guide journal targeting.

Instructions

Pre-submission scoring of an academic paper from its title and abstract. Returns Tier 1, Tier 2 and Tier 3 acceptance probabilities, the detected research field, and how much evidence the estimate rests on (how many similar papers were retrieved, and whether the result is provisional), scored against a local 7.9M-paper library via FTS5 BM25 with no LLM call. Use this when the user wants a fast readiness check before submitting, or which tier of journal to target. Costs 15 Science AI Journal credits per call, charged to the API key's account; an account without enough credits gets HTTP 402 and is not charged, and a repeat of a recent run returns the saved result's link without charging. The probabilities are estimates from similar published papers, not a decision: present them as a rough guide. Calls are rate-limited per API key; a refused call (401, 402, 422, 429, 503) is not charged and the error says what to do. If the server answers that this tool is not available through MCP yet, nothing was charged: run Pre-Check in the web app at scienceaijournal.com/scorer instead.

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": {
      "title": "<title>",
      "abstract": "<abstract>"
    },
    "name": "pre_check_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoSet to true to score a title + abstract this account already ran recently. Without it, a repeat returns a pointer to the saved result and is not charged.
titleYesPaper title (required unless booleanQuery is supplied).
abstractYesPaper abstract (required unless booleanQuery is supplied).
fullTextNoOptional full manuscript text. Pass when available; results are more accurate.
keywordsNoOptional author-supplied keywords; comma-separated.
abstractOnlyNoSet to false to score against fullText. Default true. Ignored when fullText is absent.
booleanQueryNoOptional Elicit-style Boolean query (Phase 0 / P0a). Example: `("persistent homology" OR "algebraic topology") AND topological`. When supplied, bypasses bag-of-words token extraction and feeds the lowered FTS5 string directly. Parse failures return HTTP 400 with the character position of the error.
acknowledgeLowEnglishNoThe library is English-language: a text that does not look like English is refused with HTTP 422 and not charged. Set to true to run it anyway (charged as usual; expect a rough result).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.4
    • changedInput schema / properties / abstract / description
      Previous value: -"Paper abstract (required)."New value: +"Paper abstract (required unless booleanQuery is supplied)."
    • addedInput schema / properties / acknowledgeLowEnglish
      Added value: +{
      +  "description": "The library is English-language: a text that does not look like English is refused with HTTP 422 and not charged. Set to true to run it anyway (charged as usual; expect a rough result).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / booleanQuery
      Added value: +{
      +  "description": "Optional Elicit-style Boolean query (Phase 0 / P0a). Example: `(\"persistent homology\" OR \"algebraic topology\") AND topological`. When supplied, bypasses bag-of-words token extraction and feeds the lowered FTS5 string directly. Parse failures return HTTP 400 with the character position of the error.",
      +  "maxLength": 2000,
      +  "type": "string"
      +}
    • addedInput schema / properties / force
      Added value: +{
      +  "description": "Set to true to score a title + abstract this account already ran recently. Without it, a repeat returns a pointer to the saved result and is not charged.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / title / description
      Previous value: -"Paper title (required)."New value: +"Paper title (required unless booleanQuery is supplied)."
  2. First observedv0.1.3

TDQS

A4.4/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so well: 15 credits per call, HTTP 402 when credits are short with no charge, deduped repeats returning a saved-result link without charge, per-key rate limits, and a list of non-charged refusal codes (401/402/422/429/503). It even flags the epistemic caveat that probabilities are estimates from similar papers, not a decision.

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?

Purpose and output are front-loaded in the first two sentences, with cost and error behavior following in descending order of importance. The paragraph is dense but each sentence carries operational value; only the credit/error recital runs slightly long.

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 eight parameters and no output schema, the description compensates by describing the return payload (tiers, field, evidence count, provisional flag) and the billing/error contract. It also provides a fallback path when the tool is unavailable over MCP, leaving no major question an agent would need before calling it.

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 description coverage is 100%, so every parameter including force, fullText, abstractOnly, booleanQuery and acknowledgeLowEnglish is already documented in the schema. The description adds only indirect context via the repeat-run/charging explanation, which gives the agent a reason to care about force but no new syntax or format detail. Baseline 3 is appropriate.

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 ('Pre-submission scoring of an academic paper from its title and abstract') and enumerates what comes back: Tier 1/2/3 acceptance probabilities, detected field, and evidence weight. It also names the mechanism (local 7.9M-paper library, FTS5 BM25, no LLM call), which separates it from the LLM-based sibling ai_review_paper and from recommend_journals.

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?

Gives an explicit trigger: 'Use this when the user wants a fast readiness check before submitting, or which tier of journal to target.' It also routes the agent to the web app when MCP is unavailable. It stops short of naming a sibling alternative or stating when-not to use it (e.g., versus ai_review_paper for deeper critique).

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