Skip to main content
Glama
scholar-search

scholar-search

by hui-xu-ai

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

NameRequiredDescriptionDefault
urlsYes
fieldsNoKeep only these keys on each record. `url` and the quota pair are always kept.
channelNo
include_abstractNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.12.36

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses serial execution and per-record cost, that one failure does not abandon the batch, the exact response envelope, and the critical exception that a risk block aborts the batch instead of being reported as ok. This is information an agent could not get from any structured field.

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?

Well front-loaded: purpose, then cost model, then parameters, then response shape, then the block exception. Some words are spent on implementation history ('this loop used to file it under ok: true') rather than agent-facing facts, which is the main trimming opportunity.

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

Completeness4/5

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

An output schema exists, yet the varying success/failure envelope and the blocking case genuinely warrant explanation, and both are covered. The only gap is the undocumented `channel` parameter relative to a four-parameter tool.

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 only 25%, so the description must compensate. It adds real meaning for `include_abstract` (default off, ~14 KB per twelve abstracts, multiplies by batch size) and defers `fields` to `detail`, but `channel` is left completely undocumented in both schema and description.

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?

Opens with a specific verb and resource ('Fetch several records in one call') and implicitly contrasts with the single-record `detail` tool it repeatedly references. An agent can tell this is the batch counterpart without opening the schema.

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?

Implies the batch use case and explicitly argues that this is 'the call that most needs' abstracts enabled, plus guidance that a caller can retry only failed records. It never states an explicit exclusion such as 'use detail for a single URL', so the routing rule is left implicit.

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