Skip to main content
Glama
Sign In

switch

by ai.switchapp
OverviewDiscussionsAdmin

Shot Log Price

quote_shot_log
Read-onlyIdempotent

Say what it costs to log the shots of your Editor project (or one shared with you): every clip on the video track becomes SH001, SH002 … with its timeline and source in/out, and Gemini watches each one for a short editorial description, shot size, angle, subjects, setting, action, objects and sound. Nothing is charged by this call.

Input Schema

NameRequiredDescriptionDefault
relogNotrue = the price to read every shot again.
trackNoThe video track to log, default V1.
project_idNoThe Editor project id (list_editor_projects). Omit for your latest project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / track / description
      Previous value: -"The video lane to log, default V1."New value: +"The video track to log, default V1."
  2. Changed1 schema field changed
    • addedInput schema / properties / relog
      Added value: +{
+  "description": "true = the price to read every shot again.",
+  "type": "boolean"
+}
  3. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive), so the bar is lower, and the description still adds the crucial billing fact that nothing is charged and describes what the priced operation analyzes per clip (Gemini description, shot size, angle, subjects, etc.). Respected: it does not contradict the read-only annotation.

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

Conciseness3/5

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

Purpose is front-loaded, but the long enumeration of Gemini analysis fields (shot size, angle, subjects, setting, action, objects, sound) describes the downstream logging operation rather than the quote itself, making the definition wordier than a price tool needs.

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?

No output schema exists, so the description should say what the quote returns (units, per-clip vs total, format). It explains what is being priced but never the shape of the price response, leaving an agent guessing about the return value.

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%, so relog, track and project_id are already documented in the schema; baseline 3 applies. The description adds little parameter meaning beyond reiterating project scope ('your project or one shared with you').

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 verb and resource (quote the cost of logging shots in the Editor project) and scopes it to 'your project or one shared with you'. It does not name the sibling that actually performs the operation (log_shots), so the boundary is clear only by inference.

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?

The final sentence 'Nothing is charged by this call' implies this is a pre-flight estimate rather than the execution, but there is no explicit directive such as 'use log_shots to actually log' or when this quote is required before logging. Usage is implied, not stated.

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

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