Skip to main content
Glama
Sign In

aicut

by pro.aicut
OverviewDiscussionsAdmin

Write a niche's script (free preview)

preview_niche_script

Writes the scenes of a plan_required niche for the user to read before the paid run (generate_from_niche with its plan_id). FREE: no go needed. Start with slug, revision, values (and duration_seconds if asked); it waits about 20 s; then follow its next_step. The flow: get_recipe niche-run.

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

Input Schema

NameRequiredDescriptionDefault
slugNoThe niche's `slug`: starts a preview.
valuesNoAs on `generate_from_niche`.
plan_idNoReads that preview instead (send it alone).
revisionNoThe `revision` you read (`list_niches` with `slug`).
duration_secondsNoOne of the niche's `settings.options.durations_seconds`; longer costs more. Only if the user asked; never to save tokens, never carried over.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the call is free, needs no 'go', waits about 20 seconds, and yields a `next_step` to follow. That is useful behavioral context for a generation-style tool. It still does not describe what the preview output contains or whether previews persist, but the annotations already cover safety and openness.

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?

The description is short and front-loads the purpose before usage details. It is efficient, but the final fragment 'The flow: `get_recipe` `niche-run`.' is cryptic and the backtick-heavy style may slow comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a generation tool with five parameters, an alternate `plan_id` mode, a ~20 second wait, and no output schema, the description leaves important gaps. It explains when to call it but not what the preview returns or how the `plan_id` read-back path behaves.

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 description coverage is 100%, so parameter meaning is already well documented. The description adds the starting set (`slug`, `revision`, `values`) and a caution about `duration_seconds`, but most of that caution duplicates the schema's own wording. The `plan_id` parameter is not addressed in the description at all.

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?

The description uses a specific verb and resource: 'Writes the scenes of a `plan_required` niche for the user to read before the paid run'. It explicitly contrasts this with `generate_from_niche`, so an agent can distinguish it from the paid sibling without opening the schema.

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?

It clearly states when to use this tool: before the paid run, as a free preview, starting with `slug`, `revision`, and `values`. It also tells the agent to follow `next_step` and mentions the `get_recipe` / `niche-run` flow. However, it never explains the `plan_id` alternate mode, leaving a usage branch undocumented.

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

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