Marsell

Quote a series' month

series_quote

Read-only

What a video series costs: the tokens per episode (its film's budget, plus the day's news search and pick for a series from the news) and per month at its cadence (the most slots a month holds), against the owner's plan tokens, and what that costs the owner in dollars a month (the price of their plan when it holds it, else of the smallest plan that does), and the spend setting each episode needs to be made and posted without a card each day. Give series for one that exists (its first scheduled video type, as it is set now), or format, looks, cadence and topic for one not made yet. How an episode is made sets its budget: one in AI video costs much more than one in motion graphics made in code. Before creating or starting one, quote the month with series_quote and tell the owner the tokens each episode and the month may use, whether their plan holds it, and what it costs them in dollars a month (costs_the_owner: the price of the plan that holds it). A film is charged what it really costs, up to its budget. 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": "series_quote"
  }
}

Input Schema

Name	Required	Description
`looks`	No	For a Short not made yet, how it is made: drawn (motion graphics made in code) or clips or mix (with AI video), each at what an episode made that way may use. Left out: the Short a new series starts with. Another length or look is quoted by making the series (free) and its type (series_video_type_set), then quoting it by name.
`topic`	No	For a series from the day's news: what the news is about. Any value quotes the news search and pick with each episode.
`format`	No	The video type, by id: original-short (a Short, 45 to 60 seconds) or original-long (a film of 8 to 12 minutes). The first when left out.
`series`	No	A series' id or exact name (series_read). Leave out to quote one not made yet.
`cadence`	No	How often it comes out. Or per_week.
`project`	No	The project's id or exact name. Optional when the account has one project.
`per_week`	No	Episodes a week, 0 to 21 (7 is every day). Instead of cadence.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false; the description adds 'Spends nothing' and explains the cost model (budget set by production method, film charged up to budget, costs_the_owner derived from plan price). This is meaningful behavioral context beyond the annotations, though it doesn't clarify response structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one massive run-on sentence with nested parentheticals, not front-loaded; key purpose and usage are buried. Information density is high, but the structure makes it hard to parse quickly.

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 7-parameter, no-output-schema, read-only quote tool, the description covers purpose, invocation timing, cost logic, and what to report to the owner. Some phrases ('the most slots a month holds') remain ambiguous, but the core information is present.

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 descriptions are already present. The description adds conditional grouping—series for an existing series (quoting its first scheduled type) vs. format/looks/cadence/topic for one not made—which helps an agent know which parameters apply together.

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 computation (tokens per episode/month, plan fit, dollar cost) for a specific resource (a video series' month). It distinguishes itself from siblings like series_read by focusing on cost, though it doesn't explicitly name alternatives.

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?

Explicitly says to call it 'Before creating or starting one' and to tell the owner the tokens/cost. Gives conditional input paths for existing series vs. not-made-yet series and a workaround for other lengths/looks. No when-not-to-use exclusions are given.

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

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