Skip to main content
Glama
Sign In

freebox

by com.usefreebox
OverviewDiscussionsAdmin

Free-finds summary for a ZIP

area_summary
Read-only

How many free finds are near a ZIP right now and their total estimated resale value. Works for everyone (no Pro required).

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": {
      "zip": "<zip>"
    },
    "name": "area_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US ZIP code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description adds two pieces of real context: data freshness ('right now') and access tier ('no Pro required'). Calling the value 'estimated resale value' also signals an approximation rather than a guaranteed figure, which prevents over-trusting the aggregate.

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?

Two short sentences: the first delivers what is returned (count plus total value) and the scope (ZIP, live), the second handles access eligibility. Nothing is repetitive or wasted.

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?

The description effectively covers return content since no output schema exists, and it flags the access tier. The 'near' radius and snapshot staleness window remain unspecified, which an agent would need to reason about.

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 coverage is 100% with the single `zip` parameter fully documented as a 5-digit US ZIP. The description adds only the notion of proximity ('near a ZIP') without defining the radius, so it brings little beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource ('free finds') and metric pair (count plus total estimated resale value) scoped to a ZIP, which distinguishes it from the listing-style find_free_stuff sibling. It never names that sibling explicitly, so the differentiation is inferred rather than declared.

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

Usage Guidelines3/5

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

'Works for everyone (no Pro required)' functions as an access prerequisite rather than a usage rule, and the 'right now' wording hints at a live-snapshot use case. There is no explicit statement of when to prefer this aggregate over find_free_stuff for item-level results.

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