Skip to main content
Glama
scholar-search

scholar-search

by hui-xu-ai

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

Search a channel for bibliographic records. Read-only.

channel: "cnki" (default; Chinese literature, Chinese queries) or "webofscience" (English literature; also accepts a Web of Science expression such as TS=(ionic AND actuator) AND PY=(2021-2026) — with no year range the last five years are applied inside the expression).

Returns a shortlist by default: abstracts are omitted unless include_abstract is true, and sort_by / min_citations / sources_only filter locally without any browser action. For the full record call detail(url), which infers the channel from the URL.

Whether detail is free depends on the channel. A Web of Science search captures full records, so a following detail is served from the cache at no cost; a CNKI search captures only the list, so the first detail for a record still needs one network action. Asking twice for the same record is always free.

An empty records list is a normal answer, not a failure: read total and dropped_year before concluding that a topic has no papers.

To get more records, the channel decides which lever exists. Web of Science has exclude_ut: pass back the UT values you already have (the last segment of each record's url) and the same query returns the records you have not seen. Do that rather than asking for a deeper page — each exclusion call is one independent request, while each page turn re-submits the query and keeps a result list open. CNKI has no exclusion field, so page is how you go further there.

total is the site's count for the query, before any local filter. With a year range applied, total: 363 alongside nine records does NOT mean "363 papers in that year" — it means the site matched 363 and this page lost 11 of its 20 to the year filter. filters.year_scope: "page" says so explicitly, and filters.dropped.year gives the count. To get a year-accurate total, put the year in the query (PY=(2026) on Web of Science, SU='x' and 年='2026' on CNKI) or use site_sort=date and read the newest page. empty_reason: "all_dropped_by_year" is the case where the whole page was filtered away.

min_impact_factor is honoured by channels that ship journal metrics (currently webofscience); records whose journal has no metric are dropped, which lowers recall by design.

Two parameters sort and they are not interchangeable:

  • site_sort (relevance / date / citation) asks the site to re-sort. That is two extra clicks and costs quota.

  • local_sort (none / citations / year) re-orders the page already in hand: free, no browser action, no quota.

Which parameters cost a fetch. The fetched page is cached as the site returned it, and every local view is derived from it, so these are free even when they change: limit, include_abstract, sort_by / local_sort, min_citations, min_impact_factor, sources_only, fields. These are a different request and cost a fetch: query, channel, site_sort, page, year_from / year_to, exclude_ut.

The older names sort and sort_by still work and mean the same thing; the new names say which one is which.

fields projects each record to the listed keys (plus url, which detail needs). include_abstract on 25 rows is tens of kilobytes; most callers want a title, a year and a DOI.

count_only drops records entirely and returns the count plus the diagnostics that explain it. Testing whether an expression parses and matches anything should not cost a full page of context: the recorded advice was limit: 1, fields: ["title"], which still returns a record.

detailA

Fetch full metadata for one record.

url may be either the URL search returned, or a bare DOI such as 10.13841/j.cnki.jxsj.2026.11.001. CNKI detail URLs are several hundred characters of encrypted signature — this one has no parameters but v= — so passing them back verbatim is easy to truncate. A DOI is short, stable and already in every record.

include_abstract defaults to false, matching search: a CNKI abstract runs about 1200 characters and a WoS one about 1000, which is most of what a detail response weighs. A caller that wants the volume, issue, pages and DOI should not pay for text it will not read. fields projects the rest, and always keeps url so the record stays followable.

A DOI costs one extra search to resolve into a URL, because that is the only way to reach the detail page. A URL that is already cached costs nothing.

channel is optional: it is inferred from the URL's host, or from the DOI prefix. Pass it only to override that inference.

detail_manyA

Fetch several records in one call.

Each lookup costs the same as detail and they run in sequence on purpose: the policy layer serialises network actions anyway, so firing them in parallel would only queue them while each held a timeout budget.

include_abstract and fields behave as in detail. A batch of twelve abstracts is roughly 14 KB, so the default is off here too — this is the call that most needs it, since the cost multiplies by the batch size.

A failure on one record does not abandon the rest — the response is {"results": [{"url", "ok", "record"|"error"}], "ok_count", "failed_count"}, so a caller can retry just the ones that failed.

A risk block is the exception: it stops the batch. detail returns a status: "blocked" payload rather than raising, so this loop used to file it under ok: true and carry on — reporting a batch as successful while the site was asking the caller to stop. AGENTS.md requires stopping on a block, and a batch that keeps visiting after one is exactly the behaviour that rule exists to prevent.

exportB

Render records as RIS or EndNote text.

With out_path, the text is written there and not returned: a caller that wants 143 records on disk should not have to pull them through its context to do it. Without it, the text comes back inline as before.

include_abstract defaults to false here even though the records may carry one. An AB field roughly quadruples an RIS entry, and an export is usually for a reference manager, which fetches abstracts on its own.

statusA

Session state: channels, cooldown, quota, bridge readiness.

brief returns only version, bridge_ready, bridge_last_seen, quota_remaining and cooldown_until. The full payload is about 500 tokens, more than a search, and three of its blocks — channel_capabilities, detail_capabilities, action_cost — are static. Poll brief while planning and read the full answer once.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation4/5

Each tool targets a distinct operation: session diagnostics (status), discovery (search), single-record retrieval (detail), batch retrieval (detail_many), and formatting (export). The only near-overlap is detail vs detail_many, but the one-vs-many distinction is explicit and unlikely to cause misselection.

Naming Consistency3/5

The set mixes noun-only names (status, detail), verb names (search, export), and noun_snake (detail_many). It remains readable, but it does not follow a single predictable verb_noun or other consistent pattern.

Tool Count5/5

Five tools is tightly scoped for a scholarly search server: one for status, one for discovery, two for record retrieval, and one for export. Each earns its place without redundancy.

Completeness4/5

The surface covers discovery, full-record retrieval (single and batch), export, and session diagnostics, which is the core lifecycle for bibliographic search. Minor gaps like no dedicated channel-listing tool or related-work traversal are workable through existing tools or outside the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessOutdated data