Skip to main content
Glama

Count the hours of video that meet a spec

match_video_spec
Read-only

Find out how many hours of video on Graunt meet a spec, and in which categories. Give the requirements that matter (shortest side, frame rate, clip length, sound, on-screen text, overlays, first and last shots, freezes, slowed footage, releases, clearances, AI generation, uses, delivery); leave the rest out. Returns matching hours per category and per listing: hours that meet every requirement on recorded evidence, and hours that meet every requirement the evidence covers but lack evidence for one or more. Each listing carries its list price and any rate per hour and volume tier it is stored with, its hours per category with what each category alone costs where it sells by category, the spec's categories priced as one order, its delivery modes and where each number comes from. Thresholds snap to fixed steps and the answer says which were applied. Give hours_wanted to also get a proposal: whole listings across sellers that reach those hours on recorded evidence, lowest price per measured hour first, each at its seller's own price, for the person you work for to add to their cart. Nothing is held, and short_units is the gap the proposal leaves, not a statement about what Graunt holds.

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

Input Schema

NameRequiredDescriptionDefault
qNoWords in the listing, as listing search reads them: an activity or subject the categories do not name. These are the seller's words.
usesNoUses the listing must allow, all of.
audioNoSound required, or no sound.
limitNoListings returned; default 50, cap 200. Totals and categories count every listing.
min_fpsNoFrames a second, at least: steps 24, 25, 30, 48, 50, 60, 120 (23.976 counts as 24).
no_loopsNoLeave out clips with a stretch that repeats earlier footage.
subjectsNoWhat the footage shows, any of.
no_slowedNoLeave out clips with a slowed-footage signal.
sublicenseNoONE_CLIENT_PREAUTHORIZED: the listing must allow buying for one client, named privately at purchase (D-651).
native_onlyNoLeave out clips with an upscale signal.
camera_viewsNoThe camera view the listing declares, any of.
hours_wantedNoThe hours you need across listings. The answer then carries a proposal: whole listings across sellers that reach them on recorded evidence, each at its seller's own price.
no_grayscaleNoLeave out black-and-white clips.
orientationsNoPicture orientations, any of.
audio_checkedNoThe sound runs the length of the picture, with no dual mono and no silent channel.
color_checkedNoColor tags present and consistent, and luma inside the tagged range.
music_clearedNoMusic and audio cleared or not applicable.
delivery_modesNoDelivery modes, any of: DOWNLOAD from Graunt, or LINKS or SEALED from the seller's storage.
no_ai_generatedNoOnly clips the seller declares no AI model generated.
person_releasesNoClips that show people need signed releases (SIGNED), or releases the seller holds (ON_FILE).
min_clip_secondsNoClip length, at least (seconds): steps 5, 10, 30, 60, 120, 300, 600, 1200, 3600, 14400.
people_on_cameraNoNONE: only clips with nobody on camera. SUBJECT: only clips with people as the subject.
min_listing_hoursNoOnly listings with at least this many hours that meet the spec or might.
min_short_side_pxNoShortest side of the picture, at least (pixels): steps 240, 360, 480, 720, 1080, 1440, 2160, 4320.
property_releasesNoProperty releases where one is needed.
clip_seconds_underNoClip length, under (seconds), on the same steps.
text_seconds_underNoOn-screen text stays on screen under this long (seconds): steps 0.5, 1, 2, 5.
black_seconds_underNoBlack under this long in total (seconds): steps 0.5, 1, 2, 5.
event_venue_clearedNoEvent or venue cleared or not applicable.
max_cuts_per_minuteNoScene cuts a minute, at most: steps 0, 1, 2, 5, 10.
text_area_under_pctNoOn-screen text covers under this share of the frame (percent): steps 1, 2, 5, 10.
freeze_seconds_underNoNo frozen stretch this long or longer (seconds): steps 0.5, 1, 2, 5.
edge_shot_min_secondsNoEach clip's first and last shots last at least this long (seconds): steps 1, 2, 3, 5.
no_identifiable_minorsNoLeave out clips the seller says show identifiable minors.
third_party_ip_clearedNoLogos and trademarks cleared or not applicable.
overlay_share_under_pctNoClips with an overlay signal (a logo or watermark) stay under this share of a listing's matching hours (percent): steps 0, 5, 10, 20, 50.
min_audio_sample_rate_hzNoSound sample rate, at least: steps 44100, 48000, 96000.
processed_area_under_pctNoBlack bars and fixed overlays cover under this share of the frame (percent): steps 1, 5, 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / delivery_modes / description
      Previous value: -"Delivery modes, any of: DOWNLOAD from Graunt, or LINKS from the seller's storage."New value: +"Delivery modes, any of: DOWNLOAD from Graunt, or LINKS or SEALED from the seller's storage."
    • changedInput schema / properties / delivery_modes / items / enum
      Previous value: -[
      -  "DOWNLOAD",
      -  "LINKS"
      -]New value: +[
      +  "DOWNLOAD",
      +  "LINKS",
      +  "SEALED"
      +]
  2. Changed4 schema fields changed
    • addedInput schema / properties / hours_wanted
      Added value: +{
      +  "description": "The hours you need across listings. The answer then carries a proposal: whole listings across sellers that reach them on recorded evidence, each at its seller's own price.",
      +  "type": "number"
      +}
    • changedInput schema / properties / people_on_camera / description
      Previous value: -"NONE: only clips with nobody on camera."New value: +"NONE: only clips with nobody on camera. SUBJECT: only clips with people as the subject."
    • changedInput schema / properties / people_on_camera / enum
      Previous value: -[
      -  "NONE"
      -]New value: +[
      +  "NONE",
      +  "SUBJECT"
      +]
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "Words in the listing, as listing search reads them: an activity or subject the categories do not name. These are the seller's words.",
      +  "type": "string"
      +}
  3. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the read-only and open-world annotations, the description discloses rich behavior: two evidence-based matching categories, per-listing pricing and provenance, threshold snapping, proposal sorting by price per measured hour, and the important caveat that nothing is held and short_units reflects the proposal gap rather than Graunt inventory. This adds substantial context an agent could not infer from annotations alone.

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 front-loaded with purpose and its dense content is appropriate for a complex 38-parameter tool with no output schema. It could be easier to scan if the return-value and proposal details were split into shorter structured sentences, but almost every sentence earns its place.

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 complex matching, pricing, and proposal tool with no output schema, the description covers the essential return values, evidence distinction, price and provenance fields, threshold snapping, proposal behavior, and the no-hold caveat. An agent can understand what the tool returns and how to request a proposal without needing more 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%, so the input schema already documents all 38 parameters and their enums, defaults, caps, and step values. The description reinforces that unneeded requirements may be omitted and that hours_wanted triggers a proposal, but those semantics are also present in the schema, so it adds little beyond the baseline.

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 gives a specific verb and resource: 'Find out how many hours of video on Graunt meet a spec, and in which categories.' It also clearly describes the unique aggregation and proposal output, which implicitly separates it from plain asset retrieval tools, but it does not explicitly name or contrast any sibling tool.

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?

It gives useful parameter-level guidance, such as supplying only the requirements that matter and adding hours_wanted to request a proposal. However, it does not state when to use this tool instead of alternatives like search_assets, nor does it describe when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources