Skip to main content
Glama

list_formats

Read-only

List supported CAD drawing formats for reading and writing, showing paid outputs and beta features, without using API calls or requiring an API key.

Instructions

List the drawing formats: extensions, which can be read (2D or 3D) and written, which outputs are paid (use 10 calls), and which are beta. Uses no calls and needs no API key.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only safety profile is covered. The description's genuine addition is cost semantics: zero calls consumed and no API key required, plus the note that some outputs cost 10 calls. That is useful context beyond annotations, but it does not describe the shape of what comes back (per-format records vs a flat list).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with no filler, and the resource is front-loaded before the parenthetical detail. The nested clauses (2D/3D, paid, beta) are slightly crammed together but each carries distinct information. Nothing is redundant enough to cut.

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?

The tool is trivial to invoke (0 params), and with no output schema the description correctly takes on the job of enumerating what the results contain: extensions, readability and writability, pricing, beta status. The remaining gap is the return structure and ordering, which matters less for a short static reference list.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies in principle. The description spends no words on inputs, which is correct for a zero-arg tool but adds no extra meaning either. A neutral baseline is the fair reading.

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?

States a specific verb (List) and resource (drawing formats) and then enumerates the returned facets: extensions, read/write capability with 2D/3D distinction, paid status, and beta status. That is far more than a tautology. It stops short of naming any sibling tool, so an agent must infer that this is the discovery/pre-flight call rather than, say, convert_drawing.

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?

'Uses no calls and needs no API key' strongly implies this is a free pre-flight call to run before costly operations, including the ones that 'use 10 calls'. However, it never says explicitly when to call this instead of alternatives, nor does it name any alternative tool as a routing target. Usage is 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.