detail_many
Fetch multiple CNKI literature records in one batched call, returning per-record success or failure so failed lookups can be retried without repeating the whole batch.
Instructions
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.
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": {
"urls": "<urls>"
},
"name": "detail_many"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | ||
| fields | No | Keep only these keys on each record. `url` and the quota pair are always kept. | |
| channel | No | ||
| include_abstract | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||