Skip to main content
Glama

Zapmatte Green Screen Remover MCP

estimate_removal_cost

Read-onlyIdempotent

Return the exact credit cost of removing the green screen from a video of a given length. Free; does not start a job or reserve credits.

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": {
      "mode": "<mode>",
      "durationSeconds": "<durationSeconds>"
    },
    "name": "estimate_removal_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesQuality id from list_removal_options: "standard" or "fine".
durationSecondsYesLength of the video in seconds (decimals allowed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the description's added value is the cost/no-side-effect guarantee: free, no job started, no credits reserved. That is meaningful behavior beyond the structured fields, though it doesn't say whether the estimate is stable over time or how it relates to actual billing.

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?

Two short sentences with the outcome stated first and the side-effect guarantee second; no filler, no restatement of the title.

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 two-parameter read-only estimator with no output schema, the description covers what is returned (the exact credit cost), the cost of calling it (free), and its side effects (none). Nothing an agent needs to invoke it correctly is missing.

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%, with both parameters fully documented including the valid mode ids and the duration bounds. The description only echoes duration ("of a given length") and says nothing about mode, so it adds little beyond the schema.

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?

States a specific verb and resource ("Return the exact credit cost of removing the green screen from a video") with a clear scope qualifier ("of a given length"). The clause "does not start a job or reserve credits" distinguishes it from the sibling that actually performs the removal.

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

Usage Guidelines4/5

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

"Free; does not start a job or reserve credits" gives clear context that this is the pre-flight check to run before a paid removal, but it never explicitly says "call this before remove_green_screen" or names an exclusion. Usage is strongly implied rather than stated.

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