Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

generate_direct_checkout_link

Read-onlyIdempotent

Build a pre-filled Shopify cart permalink for one or more book or bundle variant IDs, creating a one-click checkout on humanedgepress.com with optional note or user-supplied discount code.

Instructions

Build a pre-filled 1-click Shopify cart permalink on humanedgepress.com for one or more book or bundle variant IDs (from search or book details). Only pass a discountCode that the user explicitly provided.

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": {
      "items": "<items>"
    },
    "name": "generate_direct_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional gift or order note
itemsYesBooks or bundles to add to cart
discountCodeNoOptional user-supplied discount code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavior beyond that: the link is pre-filled and 1-click on a specific storefront, and discounts must never be invented, which is a real constraint an agent could otherwise violate.

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?

Two tight sentences with the core action and storefront front-loaded, followed by the one real constraint. Nothing is redundant or padded.

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?

With three parameters, no nested objects and no output schema, the definition covers what the agent needs to invoke it correctly. The only minor gap is that the return value is only implied by 'permalink' rather than stated as a URL string to hand to the user.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description earns above that by telling the agent where variantId values should be sourced and by strengthening the discountCode rule from 'user-supplied' to 'explicitly provided.' The note and quantity parameters are left entirely to the schema, which is acceptable given full coverage.

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 gives a specific verb-plus-resource: build a pre-filled 1-click Shopify cart permalink on humanedgepress.com for book or bundle variant IDs. An agent can immediately tell this generates a shopping link rather than performing a search or fetching book metadata, which separates it from the search and details siblings.

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?

It states where the variantIds come from (search or book details) and adds a clear guardrail: only pass a discountCode the user explicitly provided. It does not name an explicit alternative or a when-not condition, so it stops 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.