Skip to main content
Glama

Print platform specs

get_platform_specs
Read-onlyIdempotent

Use this when an author asks what Amazon KDP, IngramSpark or Lulu require for a print book: available trim sizes, interior bleed, margin and gutter minimums, page-count limits by binding and paper, spine-text minimum, and file rules (embedded fonts, 300 DPI images, file size, color, no encryption). Returns the platform's full requirement list with links to its official documentation.

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": {
      "platform": "<platform>"
    },
    "name": "get_platform_specs"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPrint platform: 'kdp' (Amazon KDP), 'ingramspark' or 'lulu'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: that the return is the platform's full requirement list with links to official documentation, which tells the agent the answer is authoritative and self-contained rather than a summary.

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?

The trigger clause is front-loaded and the sentence has no filler. The long enumeration of covered requirements is dense but functional — it lets the agent decide whether this tool answers the author's question without a follow-up lookup.

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

Completeness5/5

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

For a one-parameter reference lookup with no output schema, the description covers the trigger, the full scope of returned content, and the return form (requirement list plus official doc links). Nothing an agent needs to select or call it correctly 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?

The single 'platform' parameter is fully documented in the schema, including the enum values and their expansions ('kdp' (Amazon KDP), 'ingramspark' or 'lulu'). The description only restates those same three platform names, adding no format, default, or edge-case meaning beyond the schema, so the high-coverage baseline of 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 trigger and resource ('what Amazon KDP, IngramSpark or Lulu require for a print book') and enumerates exactly what is covered: trim sizes, bleed, margin/gutter minimums, page-count limits, spine-text minimum, and file rules. This clearly separates it from the sibling calculators, which compute a value rather than return a requirement reference.

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 opening 'Use this when an author asks what ... require' gives a concrete, explicit activation condition tied to a user intent. It stops short of naming when-not conditions or pointing to calculate_cover_size / calculate_spine_width for derived numbers, so it falls short of a full routing statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources