Skip to main content
Glama

List formats

list_formats
Read-onlyIdempotent

Lists the file formats Converter Studio converts and what each converts to. Give "from" (a format id such as "heic" or "mp4") to see the targets of one format. Needs no account.

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

Input Schema

NameRequiredDescriptionDefault
fromNoOnly this source format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is low. The description still adds real context: no account is required, and the `from` variant returns a narrower result set rather than the full matrix.

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, front-loaded with what the tool returns, then the filter behavior, then the auth note. Nothing is padded or redundant.

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 one-optional-enum, read-only lookup with no output schema, this covers purpose, filter behavior, and auth. It omits only the shape of the no-argument response (full mapping), which is a minor 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?

Schema coverage is 100% and the enum already lists every valid id, so baseline would be 3. The description earns more by explaining the parameter's effect (returns the targets of that one format) rather than just repeating its type.

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 ("Lists the file formats Converter Studio converts") and adds the payload semantics ("what each converts to"), which no sibling name implies. An agent can distinguish this discovery tool from convert and confirm_conversion immediately.

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?

Explains the conditional usage of the optional parameter ("Give 'from' ... to see the targets of one format") and adds an access precondition ("Needs no account"). It does not explicitly say when to call this instead of convert, though the discovery intent is clear.

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.