scholar-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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 An empty records list is a normal answer, not a failure: read To get more records, the channel decides which lever exists. Web of
Science has
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:
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: The older names
|
| detailA | Fetch full metadata for one record.
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.
|
| detail_manyA | Fetch several records in one call. Each lookup costs the same as
A failure on one record does not abandon the rest — the response is
A risk block is the exception: it stops the batch. |
| exportB | Render records as RIS or EndNote text. With
|
| statusA | Session state: channels, cooldown, quota, bridge readiness.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.