Skip to main content
Glama

Cannon Studio

by app.cannonstudio

Get Cannon Studio Pricing Context

get_pricing_context
Read-onlyIdempotent

Explain public Cannon Studio pricing, credits, plans, and usage tradeoffs. Public read-only: no auth, no state changes, no charges; use list_offerings or get_checkout_link only when the user asks for available purchase paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planNoOptional plan or tier name the user mentioned, such as free, hobbyist, creator, pro, team, or enterprise.
use_caseNoOptional workload or scenario to price, such as UGC ads, AI video, 3D generation, narration, team workflows, or developer API automation.
media_typeNoOptional media category, such as image, video, 3D, audio, narration, subtitles, lip sync, or post-production.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYes
sourcesYes
summaryYes
use_caseYes
media_typeYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds valuable context: 'no auth, no state changes, no charges.' This goes beyond annotations by clarifying the operational and cost implications, which is especially useful for a pricing tool.

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?

The description is two sentences—first stating purpose, then usage guidelines and safety. Every word earns its place, and the key information is front-loaded. No filler.

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?

For a read-only explanatory tool with a rich output schema and comprehensive annotations, the description fully covers what the tool does, when to use it, and important caveats (public, no charges). The output schema handles return details, so nothing is missing in context.

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% with each parameter clearly documented. The description does not add extra parameter semantics, but it doesn't need to since the schema carries the full load. Baseline 3 is appropriate.

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 clearly states a specific verb and resource: 'Explain public Cannon Studio pricing, credits, plans, and usage tradeoffs.' It distinguishes this from sibling tools by emphasizing 'public read-only' versus purchase-path tools like list_offerings and get_checkout_link.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs when to use alternatives: 'use list_offerings or get_checkout_link only when the user asks for available purchase paths.' This gives clear context and exclusions, making it easy for an agent to route correctly.

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

All Cannon Studio toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct resource or action: status, comparison, creation, estimation, fetching, API docs, checkout, generation polling, model availability, pricing, capabilities, offerings, toolkits, workflow recommendation, and knowledge search. Even the get_* and list_* tools have clear, non-overlapping purposes.

Naming Consistency3/5

Most tools follow a verb_noun pattern (create_generation_request, list_offerings, get_checkout_link), but there are exceptions: api_status is a noun, and fetch and search are single verbs without an object. The mix of get/list/compare/recommend/search/fetch is readable but not perfectly uniform.

Tool Count5/5

15 tools is at the upper bound of the well-scoped range, but each tool serves a clear, distinct purpose in the Cannon Studio domain—from estimation and creation to knowledge retrieval and workflow recommendation. No tool feels redundant or superfluous.

Completeness3/5

The surface covers creation, estimation, polling, knowledge, and commercial operations, but the generation lifecycle is incomplete: there is no update, cancel, or list tool for generation requests, and the create tool explicitly cannot be cancelled through MCP. This is a notable gap for agents managing ongoing work.

Resources