Skip to main content
Glama
Sign In

4OVER4

by com.4over4
OverviewDiscussionsAdmin

Find 4OVER4 products that go together

find_matching_print_products
Read-onlyIdempotent

Finds 4OVER4 print products that pair with one product, such as letterhead and envelopes with business cards or stickers with packaging; use it when someone asks what goes with a print product. For products like it use find_similar_products; for a whole campaign use marketing_kit. Requires the product slug. Returns the recommended pairing products with slug, name and From price. Customer phrases: "what goes with these business cards", "matching envelopes for my invitations".

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": {
      "slug": "<slug>"
    },
    "name": "find_matching_print_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug, from the slug field of a show_products, recommend or find_similar_products result, e.g. standard-business-cards.

Output Schema

NameRequiredDescriptionDefault
dataNoProducts that pair with one product.
linkNoThe page on www.4over4.com to continue on: order, upload and checkout happen there.
summaryYesThe facts of the result in plain sentences.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds that the slug is required and enumerates the returned fields (slug, name, From price), plus sample customer phrasings. Minor gaps only: no note on empty results or error behavior when the slug is unknown.

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?

Purpose and usage lead, alternatives follow, then the return shape and finally sample utterances. Semicolon-delimited clauses keep it dense without waste; no sentence is filler.

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?

A single-parameter read-only lookup whose annotations carry the safety profile and whose output schema defines the return values. The description still supplies input provenance and intent routing, so nothing an agent needs to 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?

Only one parameter, and the schema already documents it at 100% coverage, including its origin from a show_products/recommend/find_similar_products result. The description's "Requires the product slug" restates the schema rather than adding new meaning, so the 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?

Names a specific verb and resource ("Finds 4OVER4 print products that pair with one product") and immediately scopes it with concrete examples (letterhead/envelopes with business cards, stickers with packaging). It is clearly distinguishable from find_similar_products and marketing_kit, which it names.

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

Usage Guidelines5/5

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

Explicitly states when to use it ("when someone asks what goes with a print product") and routes the agent to the correct siblings for adjacent intents: find_similar_products for lookalikes, marketing_kit for a whole campaign. Nothing is left to inference.

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

All 4OVER4 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources