Skip to main content
Glama
Sign In

freebox

by com.usefreebox
OverviewDiscussionsAdmin

Create an alert

create_alert

Creates a Freebox alert that flags matching free finds. Provide at least a keyword or a category. Pro only.

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

Input Schema

NameRequiredDescriptionDefault
keywordNoKeyword to match in the listing title/description.
categoryNoCategory to match, e.g. 'furniture'.
frequencyNoHow often to notify (default daily).
min_profitNoOnly alert on finds with est. profit >= this (USD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, non-idempotent write (destructiveHint=false, idempotentHint=false), and the description adds genuine unannotated context: a Pro-plan requirement and a validation constraint on matching criteria. It omits what is returned and whether duplicate alerts are allowed, but the key behavioral facts are covered.

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?

Three short sentences, front-loaded with purpose and effect, then the calling constraint, then the access gate. No filler.

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?

For a four-parameter create tool with no output schema, the description covers purpose, minimum input requirement, and plan gating. Remaining gaps (return value such as an alert id, and default notification channel) are minor given full schema coverage.

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 parameter meaning is already documented; the description additionally supplies the cross-field constraint (at least one of keyword or category) that the schema does not express via required or anyOf, which is real added value.

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 (creates a Freebox alert) plus its effect (flags matching free finds), which an agent can immediately tell apart from the sibling alert tools delete_alert and my_alerts.

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

Usage Guidelines4/5

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

Gives two concrete calling conditions: 'Provide at least a keyword or a category' and 'Pro only.' It doesn't name the alternative tools for viewing or removing alerts, but the when-to-use context is clear.

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

All freebox 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