Skip to main content
Glama

get_supported_formats

Lists all supported input and output file formats by category, or all categories, so you can confirm compatibility before conversion.

Instructions

List all supported input/output formats by category

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

Input Schema

NameRequiredDescriptionDefault
categoryNoCategory to list formats for (default 'all')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full disclosure burden. "List" implies a non-mutating enumeration of a static catalog, as does the fact that no output schema exists, but the description never states read-only semantics, the response shape, or how results are grouped beyond the phrase "by category".

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 tight sentence with the resource front-loaded and no redundant wording. Nothing could be removed without losing meaning.

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

Completeness3/5

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

For a one-parameter, zero-required lookup tool this is close to sufficient, but with no output schema the description should indicate what the listing returns (format names only? grouped buckets? capabilities per format?). That gap keeps it at minimum-viable completeness.

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 description coverage is 100% and the sole optional parameter already carries a description plus a 19-value enum with a documented 'all' default. The description's phrase "by category" reinforces that the parameter narrows the listing, but adds no syntax or behavior beyond the schema — baseline 3 applies.

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?

"List all supported input/output formats by category" states a specific verb (List), a specific resource (supported input/output formats), and the organizing dimension (category). This clearly separates it from every convert_* sibling, which performs transformations rather than enumeration, though the description never explicitly names a sibling.

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 a discovery/lookup tool useful before picking a convert_* call. There is no explicit when-to-use statement, no mention that category can be narrowed versus the default 'all', and no exclusions.

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