Skip to main content
Glama
tobbaz

kb-newspapers-mcp

by tobbaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_newspaper_page_image

Generate direct image URLs and IIIF links for a specific digitized newspaper page by specifying image service, package, page, part, and width.

Instructions

Generate direct image URLs and IIIF links for a specific newspaper page.

Args:
    image_service_id: IIIF image service URL returned from search_newspapers (e.g. 'https://data.kb.se/iiif/3/dark-30466%2Fbib4345612_18620716_0_s_0003.jp2').
    package_id: Package ID of the newspaper issue (e.g. 'dark-30466' or 'dark-37858').
    page_number: Page number within the issue (e.g. 1, 3, 4).
    part_number: Part/section number (default 1).
    width: Desired pixel width for the preview image (e.g. 1200 for readable size, 300 for thumbnail).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNo
package_idNo
page_numberNo
part_numberNo
image_service_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

There are no annotations, so the description carries the full disclosure burden. It clearly says the tool generates URLs/IIIF links and documents defaults, but it does not explicitly state that the operation is read-only, what happens on invalid input, or whether any network request is made to resolve the image. That is acceptable for a simple URL-generation tool but not fully transparent.

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?

The purpose is stated in one sentence, followed by a compact, well-organized argument list. Every line adds useful information and no filler or repetition is present.

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 tool with an output schema and richly documented parameters, the description is nearly complete: it includes source context for the main input, defaults, and typical usages. The only gaps are explicit alternative routing and edge-case behavior, which are minor given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description compensates fully by explaining each of the five parameters with a purpose and representative examples. It adds meaning well beyond the bare schema property names and defaults.

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?

The description opens with a specific action ('Generate direct image URLs and IIIF links') tied to a concrete resource ('a specific newspaper page'), so an agent immediately knows what the tool produces. It is also clearly distinct from the sibling tools, which search newspapers, build timelines, or search within an issue.

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?

The description provides clear context by showing where the key input comes from ('image_service_id ... returned from search_newspapers') and gives realistic usage examples for parameters such as width. It does not explicitly state when not to use this tool or name alternatives, so it stops short of full exclusion guidance.

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