Skip to main content
Glama
Sign In
AI Video Check MCP Server

AI Video Check MCP Server

by aivideocheck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get a check result

get_check
Read-only

Retrieve the status or result of an earlier AI video check using its ID. Results remain available for 24 hours, and retrieval is free.

Instructions

Get the status or result of an earlier check by its id. Free. Results are kept for 24 hours.

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": {
      "check_id": "<check_id>"
    },
    "name": "get_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two genuinely useful traits not in structured data: the call is free, and results expire after 24 hours — the latter materially affects retry/fallback behavior.

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?

Three short sentences, zero filler, with the core purpose front-loaded. Each sentence (purpose, cost, retention) earns its place.

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

Completeness4/5

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

With an output schema present, the description needn't explain return values, and it covers the key operational facts (cost, 24-hour retention, id-based lookup). Only the parameter's format and expiry failure mode remain undocumented.

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 schema has one parameter with 0% description coverage, so the description must carry the load. 'By its id' identifies the parameter as a check identifier but adds no format, source, or example; for a single-param tool this is minimal-but-adequate rather than compensating for the coverage gap.

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 verb and resource ('Get the status or result of an earlier check') and scopes it via 'by its id', so an agent knows this is a retrieval, not an initiation. It does not name the initiating siblings (check_video, check_file), so sibling differentiation is only implied by the word 'earlier'.

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?

'Of an earlier check' implies the tool is used after a check has been kicked off, which is useful contextual guidance. It stops short of explicitly saying when to use this versus the check_* siblings or what to do if the id is unknown/expired.

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

Deploy Server

Other Tools