Skip to main content
Glama
Sign In

4OVER4

by com.4over4
OverviewDiscussionsAdmin

Search 4OVER4 guides and pages

search_content
Read-onlyIdempotent

Finds 4OVER4 print guides, business print kits, product comparisons and case studies; use it when someone asks for a guide, a kit or a comparison page about printing. For support questions use search_knowledge; for products use show_products. Inputs are optional: query searches all the pages, types browses one kind, and slug with one type opens one item. Returns pages with links, or one page's detail. Customer phrases: "guides on file prep", "case studies for restaurants", "print kits for a new business".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoOne item's slug, the last segment of its page address, sent with exactly one type in types.
limitNoMost items to return.
queryNoFree-text search words.
typesNoContent types to search or browse.
offsetNoBrowse paging offset.

Output Schema

NameRequiredDescriptionDefault
dataNoEditorial pages (kits, guides, comparisons, case studies) or one page's detail.
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.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real behavioral context: three distinct operating modes (query searches all pages, types browses one kind, slug with one type opens a single item) and the shape of results (pages with links vs. one page's detail). It stops short of stating defaults for limit/offset, which is a minor gap given an output schema exists.

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?

Front-loaded with purpose and routing before details, and each sentence carries distinct information. The trailing list of customer phrases is slightly verbose but serves a retrieval-matching purpose, so it earns its place.

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?

All five parameters are optional and the description explains how they combine, what each mode returns, and when a different tool is needed. With annotations covering safety and an output schema covering return values, nothing an agent needs in order to call this correctly is missing.

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 the baseline is 3, but the description adds mode semantics beyond field-level docs: which parameter drives full-text search vs. browsing vs. single-item retrieval, and the coupling of slug with exactly one type. limit and offset are left entirely to the schema, so it is not a full 5.

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 a specific resource set ("Finds 4OVER4 print guides, business print kits, product comparisons and case studies") and explicitly separates itself from siblings by naming search_knowledge for support and show_products for products.

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 an explicit when-to-use trigger ("when someone asks for a guide, a kit or a comparison page about printing"), names two alternatives with the conditions that select them, and supplies concrete user phrasings that route to this tool.

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