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

med-lit-mcp

by junhewk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_article_page

Idempotent

Re-read one page of a fetched article within its extraction allowance (the project's wiki.max_pages), e.g. to check a quote; next_wiki_article serves the pages still to extract. Reads only (may create the project database).

Instructions

Re-read one page of a fetched article within its extraction allowance (the project's wiki.max_pages), e.g. to check a quote; next_wiki_article serves the pages still to extract. Reads only (may create the project database).

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>",
      "uid": "<uid>",
      "page": "<page>"
    },
    "name": "get_article_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesArticle uid
pageYesPage number, from 0
run_idYesRun ID from start_search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.10
    • addedInput schema / properties / page / description
      Added value: +"Page number, from 0"
    • addedInput schema / properties / uid / description
      Added value: +"Article uid"
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, which would otherwise be confusing for a 're-read' tool; the description resolves this by disclosing the one side effect ('may create the project database'). It also adds the non-obvious constraint that reads are capped by the project's wiki.max_pages extraction allowance, context the annotations do not carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loads the action, then folds in the allowance constraint, the motivating example, the sibling routing, and the side-effect caveat with no wasted clause.

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?

For a 3-parameter read tool with annotations and no output schema, the description covers purpose, alternative routing, and side effects. The main remaining gap is error behavior when the requested page exceeds the extraction allowance, which an agent would benefit from knowing before calling.

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 100%, with uid, page and run_id all documented in the schema itself (including page being 0-indexed and run_id's hex pattern). The description adds only the framing notion of an 'extraction allowance' that bounds page, which is useful but not parameter-level detail. Baseline 3 applies.

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?

States a specific verb and resource ('Re-read one page of a fetched article') and immediately scopes it against the sibling next_wiki_article, which serves pages still to extract. An agent can distinguish the two without opening either 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?

Gives a concrete motivating scenario ('e.g. to check a quote') and names the alternative tool plus the condition that selects it ('next_wiki_article serves the pages still to extract'). It stops short of stating exclusions, e.g. what happens when the page is outside the allowance, but the routing guidance is clear.

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