Skip to main content
Glama
Sign In
med-lit-mcp

med-lit-mcp

by junhewk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

next_wiki_article

DestructiveIdempotent

Get the next unextracted page of article text (a JSON header plus the page); it repeats until record_extraction records it. An article whose text changed loses its old extraction first.

Instructions

Get the next unextracted page of article text (a JSON header plus the page); it repeats until record_extraction records it. An article whose text changed loses its old extraction first.

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": {
      "run_id": "<run_id>"
    },
    "name": "next_wiki_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidNoServe only this article's pages (for a subagent that owns one article)
run_idYesRun ID from start_search
max_pagesNoPages to read for the next article, at most the project's wiki.max_pages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.1
    • changedInput schema / properties / max_pages / description
      Previous value: -"Limit pages read for the next article"New value: +"Pages to read for the next article, at most the project's wiki.max_pages"
  2. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description meaningfully explains why: 'An article whose text changed loses its old extraction first' — the destructive side effect is disclosed in plain language. It also adds pagination semantics (repeats until record_extraction records it) and the return shape, going clearly beyond the annotation flags.

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?

Two compact sentences with no filler; the core action is front-loaded and the operative lifecycle note follows. The second clause about repeated serving is slightly compressed but still parses cleanly.

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?

Covers the essential facts an agent needs: what is returned, that it is a repeat-until-recorded loop paired with record_extraction, and that stale extractions are discarded. With no output schema, one could wish for a hint on header fields or exhaustion behavior, but nothing critical is missing.

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 run_id, uid, and max_pages are already documented in the schema with their defaults and bounds. The description adds nothing about parameters, so the baseline 3 applies — the schema carries the entire burden here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: 'Get the next unextracted page of article text', and specifies what comes back ('a JSON header plus the page'). It is clear on its own, but it never distinguishes itself from the sibling get_article_page, leaving the agent to infer which one returns the sequential/unextracted view.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'it repeats until record_extraction records it' implies the intended loop with record_extraction, which is genuinely useful workflow context. However, there is no explicit statement of when to prefer this over get_article_page or list_articles, and no stated preconditions beyond run_id.

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