Skip to main content
Glama
Sign In
Tuning Engines

Tuning Engines

by cerebrixos-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_catalog_models

Browse and filter available pre-built models and datasets from the Marketplace. Retrieves name, description, base model, size, export price, and category for assets ready to export to your S3 bucket.

Instructions

List available pre-built models and datasets from the Tuning Engines Marketplace. These are platform-owned, ready-to-use assets that can be exported to your S3 bucket. Returns name, description, base model, size, export price, and category.

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter by category (e.g. 'code', 'bug-fix', 'general'). Omit to see all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.5

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but description adequately explains the read-only list operation and return fields. Lacks mention of pagination or empty results, but acceptable for a simple list.

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 sentences with no unnecessary words; clear and front-loaded with key information.

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?

Covers purpose, parameter, and return fields; no output schema needed. Missing pagination info but adequate for a straightforward list tool.

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 description coverage is 100%, and the description adds examples ('code', 'bug-fix', 'general') for the category parameter, providing extra meaning beyond the schema.

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?

Description clearly states it lists pre-built models/datasets from Marketplace, distinguishes from sibling list_models (user models) and list_inference_models by specifying platform-owned, ready-to-use assets.

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?

Describes the tool's purpose but does not explicitly state when to use vs alternatives; however, mentioning 'pre-built models from Tuning Engines Marketplace' implies context for selecting this tool over others.

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

Deploy Server

Other Tools