FARPY

quote

Lock in a price for rendering a frame sub-range of an uploaded Blender project without spending funds.

Instructions

Create a locked quote for a frame sub-range. Does not spend.

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": {
      "upload_id": "<upload_id>",
      "frame_start": "<frame_start>",
      "frame_end": "<frame_end>"
    },
    "name": "quote"
  }
}

Input Schema

Name	Required	Description
`frame_end`	Yes	Last frame, inclusive.
`upload_id`	Yes	Upload id from inspect.
`frame_step`	No	Frame step.
`frame_start`	Yes	First frame, inclusive.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 3, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It does disclose one important side-effect ('Does not spend'), but it leaves key behaviors unexplained: what 'locked' means, whether the quote expires, and whether any state changes beyond creating the quote.

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?

A single sentence with two clauses delivers the core purpose and the critical non-spend caveat. There is no filler, and the action verb is front-loaded.

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?

The description covers the basic action but omits the return value or how the quote is later consumed (e.g., by start). With no output schema and no annotations, an agent must guess what the tool returns and how it fits the workflow.

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 input schema already documents all 4 parameters with clear descriptions (e.g., 'First frame, inclusive' and 'Upload id from inspect'). The description adds the concept of 'frame sub-range', which maps to frame_start/frame_end, but it doesn't elaborate beyond the schema, so the baseline of 3 is appropriate.

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?

The description states a specific action ('Create'), a clear resource ('locked quote'), and the exact scope ('frame sub-range'). It does not explicitly name sibling tools, so it doesn't fully satisfy the 'distinguishes from siblings' bar, but 'Does not spend' gives a functional hint that separates it from likely spending/starting operations.

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?

There is no explicit when-to-use or alternative guidance. The clause 'Does not spend' implies the agent should use this tool when it wants to reserve pricing without committing, but this is left to inference rather than stated as a rule for choosing between quote and start.

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

Deploy Server