Skip to main content
Glama

Zapmatte Green Screen Remover MCP

list_removal_options

Read-onlyIdempotent

List Zapmatte quality options, credits per second of video, accepted formats and limits, and the files each job returns. Public; no key needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: the endpoint is public and requires no API key, which is an auth detail annotations cannot express, and it discloses that results include the files each job returns. It does not mention rate limits or result volume for the listings.

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?

A single front-loaded sentence names the tool's contents in order of likely usefulness, followed by a short clause on access requirements. No filler, no restatement of the tool name, nothing that could be trimmed.

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 no input parameters and no output schema, the description correctly carries the burden of telling the agent what comes back, listing the four categories of information returned. It is close to complete for so simple a tool, with only minor gaps such as whether the response is paginated or a fixed-size catalog.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description instead spends its words on what the parameterless call yields, which is the right allocation of effort here.

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 uses a specific verb (List) and enumerates the exact resource contents: quality options, credits per second, accepted formats and limits, and returned files. It is clearly a static reference/catalog lookup, distinct in kind from the action-oriented siblings such as estimate_removal_cost or create_upload, though it never explicitly differentiates itself by name.

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?

Usage is only implied: an agent can infer this is the tool to call before estimating costs or uploading, since it exposes formats, limits and credit rates. There is no explicit when-to-use or when-not-to-use statement, and no named alternative for pricing or format questions, so guidance stops at implied context plus the 'Public; no key needed' precondition.

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