Skip to main content
Glama
Sign In

4OVER4

by com.4over4
OverviewDiscussionsAdmin

4OVER4 paper weight converter

convert_paper_weight
Read-onlyIdempotent

Converts a paper weight for 4OVER4 print stock between pounds text, pounds cover, gsm and points; use it when someone compares paper thickness across units. For paper recommendations use search_knowledge. Requires the numeric weight and its unit, one of lb-text, lb-cover, gsm or pt. Returns the weight in the other units. Customer phrases: "100lb cover in gsm", "is 14pt heavy", "what is 16pt in pounds", "how thick is 300 gsm card stock".

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": {
      "value": "<value>",
      "unit": "<unit>"
    },
    "name": "convert_paper_weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesUnit of value.
valueYesThe weight to convert, e.g. 100.

Output Schema

NameRequiredDescriptionDefault
dataNoThe weight in lb text, lb cover, gsm and points.
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 establish readOnly, idempotent, closed-world, non-destructive behavior, so the description's burden is light. It adds useful context: the conversion is bidirectional across the four units and both a numeric value and a unit are mandatory. It does not mention rounding/precision of converted values, which is the one behavior an agent might still wonder about.

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?

Purpose, prerequisite, return behavior, and routing to the alternative are front-loaded in a compact block. The trailing list of customer phrases is slightly redundant with the earlier example but earns its place as trigger vocabulary for matching user utterances.

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 two-parameter, closed-world converter with an output schema, the description covers what is converted, the accepted units, the required inputs, and the fallback tool. Nothing needed to invoke it correctly is missing, and return values are covered by the output schema.

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 would be 3, but the description goes further by naming the four permitted units and tying real user phrasings ('100lb cover in gsm', 'what is 16pt in pounds') to the value/unit pair. That helps an agent map messy natural language onto the enum, which the schema alone does not.

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 first clause names a specific verb and resource ('Converts a paper weight for 4OVER4 print stock') and enumerates the exact unit set (lb-text, lb-cover, gsm, pt). It also explicitly contrasts itself with search_knowledge, so an agent can separate it from siblings without opening the 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?

It states the triggering condition ('use it when someone compares paper thickness across units') and routes a different intent elsewhere ('For paper recommendations use search_knowledge'). That is explicit when-to-use plus a named alternative, leaving little to infer.

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