4OVER4 Custom Printing

Search 4OVER4 help

search_knowledge

Read-onlyIdempotent

Answers printing and 4OVER4 support questions from 4OVER4's help center (bleed, file setup, paper, finishes, shipping, proofs, returns, custom quotes); use it for any how-to, policy or print term question. For one product's sizes or price use configure_product; for editorial pages use search_content. Requires the question as search words with the product or topic noun. Returns the answer, its source link and related questions. Customer phrases: "what is bleed", "my invitations arrived damaged", "are proofs free".

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": {
      "query": "<query>"
    },
    "name": "search_knowledge"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Most documents to return.
`query`	Yes	Search words for the question, with the product or topic noun, e.g. invitation misprint reprint refund.
`topic`	No	paper for a paper or stock recommendation, with the use case as query; free-business-cards for the 200 free business cards offer.

Output Schema

Name	Required	Description
`data`	No	The help answer, its source link and related questions.
`link`	No	The page on www.4over4.com to continue on: order, upload and checkout happen there.
`summary`	Yes	The facts of the result in plain sentences.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.3/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 value beyond them by disclosing the return shape (answer, source link, related questions) and the required query formulation, though it says nothing about result limits or how ranking works.

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 core purpose and the sibling routing are front-loaded, which is the right ordering. The trailing list of customer phrases is example-heavy filler that dilutes an otherwise tight single paragraph.

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?

An output schema exists, so the description did not need to spell out return values, yet it does so anyway. Usage, scope and alternatives are all covered for a three-parameter read tool; only minor gaps remain around limits and result behavior.

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 description coverage is 100%, so baseline is 3. The description's guidance to phrase the query as search words plus a product or topic noun largely restates what the query parameter's schema text already says, and it never mentions the topic enum or limit parameter.

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 ('Answers printing and 4OVER4 support questions from 4OVER4's help center') and enumerates the topic scope (bleed, file setup, paper, finishes, shipping, proofs, returns, custom quotes). It also explicitly distinguishes itself from two named siblings, so an agent can route without opening a schema.

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?

Gives a positive trigger ('any how-to, policy or print term question') plus two explicit exclusions with their replacements: configure_product for one product's sizes or price, and search_content for editorial pages. That is the when/when-not/alternative triad in full.

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

All 4OVER4 Custom Printing tools Inspect

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

Need Help?