Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Freezer read

freezer_read
Read-only

Lists the freezer: cards whose moment passed and left What needs you by themselves (a reply three days after its thread was posted, a trend once it stopped being current, a post or a newsletter issue three days after its day, an idea once its week ended, a picture with its post). Each with who made it, its line, why it froze, when it went in and when it leaves (30 days after). They are not waiting for the owner and are counted nowhere; freezer_take_out puts one back. Reading spends nothing.

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

Input Schema

NameRequiredDescriptionDefault
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses non-obvious behavior: each card's 30-day expiry, that frozen cards are excluded from all counts, that they aren't awaiting the owner, and that reads incur no cost. These are exactly the facts an agent needs and none are in the annotations.

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 the purpose, and every sentence contributes (membership rule, examples, per-item fields, expiry, counting behavior, restore path, cost). The parenthetical example list is long and slightly dense, which keeps it from a 5, but nothing is redundant.

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?

With no output schema, the description compensates by enumerating the returned fields (author, line, freeze reason, entry date, expiry date) and stating the 30-day lifetime. Combined with the single optional scoping parameter, an agent has everything needed to call it and interpret results.

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?

The single optional project parameter is fully documented in the schema (100% coverage, including the "optional when the account has one project" fallback), so the description adds nothing further about it. Baseline 3 applies when the schema already carries parameter meaning.

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?

Opens with a concrete verb and resource ("Lists the freezer") and then defines membership with five concrete examples plus the unifying rule (moment passed, left 'What needs you' by itself). It distinguishes itself from waiting_read by explicitly saying the items "are not waiting for the owner", and names the counterpart action tool freezer_take_out.

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?

Usage is clearly implied — call this to see what has been frozen — and the closing sentence routes the agent: restore is done via freezer_take_out, and reading is free. It stops short of an explicit "use this instead of X when..." statement, so it is strong context rather than full alternatives guidance.

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

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