4OVER4

Ways to earn 4OVER4 coins

loyalty_tasks

Read-onlyIdempotent

Lists the ways to earn 4OVER4 coins, the reward points spent on print orders; use it when someone asks how to earn coins or save on printing. For the customer's own balance use get_my_coins. The limit is optional and no sign-in is needed. Returns each task's title, short description, coins, time and page link; 100 coins are $1. Customer phrases: "how do I earn coins", "ways to get points", "what tasks give coins", "how can I save with rewards".

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": "loyalty_tasks"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Most tasks to return.

Output Schema

Name	Required	Description
`data`	No	Each loyalty task: title, short description, coins, time and its page.
`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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-redundant context: no sign-in required, the limit is optional, the coins-to-dollar conversion (100 coins = $1), and which fields come back. It stops short of describing ordering or pagination behavior of the returned task list.

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, exclusion and return shape are front-loaded and easy to scan. The trailing quoted customer-phrase list and the conversion note sit outside that flow and are somewhat repetitive, but each still aids retrieval routing.

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 no-required-parameter read-only listing tool with an output schema, the description covers the purpose, the alternative tool, authentication posture and the limit's optionality. Nothing an agent needs in order 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 optional limit parameter and schema coverage is 100%, so the schema already fully documents it with a min/max range. The description's 'the limit is optional' merely restates that required-parameters is empty, adding no format or ordering semantics beyond the schema.

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 ('Lists the ways to earn 4OVER4 coins') and immediately defines the domain ('reward points spent on print orders'), which distinguishes it from the balance-oriented sibling get_my_coins.

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?

Explicit when-to-use ('use it when someone asks how to earn coins or save on printing'), an explicit alternative with its selecting condition ('For the customer's own balance use get_my_coins'), plus concrete customer phrasings for routing.

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

All 4OVER4 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?