Skip to main content
Glama

List Features

list_features
Read-onlyIdempotent

Lists every available BGRemover Video tool with its endpoint, input schema, and credit cost so you can choose the right video background operation before submitting a job.

Instructions

This tool will list every available BGRemover Video tool, its endpoint, input schema, and credit cost. It takes no arguments.

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_features"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description earns credit for adding what the annotations cannot: that the response is a catalog containing endpoints, input schemas, and credit costs, plus the no-argument constraint. It stops short of describing pagination or output shape, but the added context is real.

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 no filler; the payload contents are front-loaded before the no-argument note, which is the right order for a reader deciding whether to call it.

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?

For a zero-parameter, read-only discovery tool with no output schema, the description covers purpose, contents returned, and the no-argument contract. A brief note on when in a workflow to call it (e.g., before selecting an operation) would close the only remaining gap.

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?

There are zero parameters and the schema is an empty object, so the baseline is 4. The description reinforces this with 'It takes no arguments,' removing any doubt that arguments are required or accepted.

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 names a specific verb and resource ('list every available BGRemover Video tool') and enumerates exactly what is returned: endpoint, input schema, and credit cost. That is clearly distinct from the operative siblings such as remove_video_background or check_credits, so an agent can identify it as the discovery tool without opening its schema.

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: the description makes clear this is a catalog of the other tools, which suggests calling it to discover endpoints and credit costs, but it never states when to prefer it over a sibling or that it should be consulted before invoking them. 'It takes no arguments' is a precondition, not routing guidance.

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