Skip to main content
Glama
hedging8563

TokenLab MCP Server

by hedging8563
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List models

list_models
Read-onlyIdempotent

Lists available models and filters them by provider, category, capability tag, or recommended non-chat task to simplify model selection.

Instructions

Lists the currently available models. Use view=compact for model selection and view=full for the existing OpenAI-compatible discovery shape. Native API calls default to full; integrations may choose compact as their default. Non-chat recommendations are available through recommended_for.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by a public capability tag.
viewNoCompact model-selection output is the MCP default. Set view to full only when the complete OpenAI-c…compact
categoryNoFilter by model category.
providerNoFilter by public model provider, for example openai, anthropic, google, or minimax.
recommended_forNoSort supported non-chat models for a task category and include recommendation evidence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.24
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "chat",
-  "embedding",
-  "translation",
-  "image",
-  "video",
-  "audio",
-  "tts",
-  "stt",
-  "rerank",
-  "3d",
-  "music"
-]New value: +[
+  "chat",
+  "embedding",
+  "translation",
+  "image",
+  "video",
+  "audio",
+  "tts",
+  "stt",
+  "rerank",
+  "3d",
+  "music",
+  "decision"
+]
    • changedInput schema / properties / view / description
      Previous value: -"Compact model-selection output is the MCP default. Set view to full only when the complete OpenAI-compatible list shape is required."New value: +"Compact model-selection output is the MCP default. Set view to full only when the complete OpenAI-c…"
  2. Changed1 schema field changedv0.6.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Changed5 schema fields changedv0.6.3
    • addedInput schema / properties / category
      Added value: +{
+  "description": "Filter by model category.",
+  "enum": [
+    "chat",
+    "embedding",
+    "translation",
+    "image",
+    "video",
+    "audio",
+    "tts",
+    "stt",
+    "rerank",
+    "3d",
+    "music"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / provider
      Added value: +{
+  "description": "Filter by public model provider, for example openai, anthropic, google, or minimax.",
+  "type": "string"
+}
    • addedInput schema / properties / recommended_for
      Added value: +{
+  "description": "Sort supported non-chat models for a task category and include recommendation evidence.",
+  "enum": [
+    "image",
+    "video",
+    "music",
+    "3d",
+    "tts",
+    "stt",
+    "embedding",
+    "rerank",
+    "translation"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Filter by a public capability tag.",
+  "type": "string"
+}
    • addedInput schema / properties / view
      Added value: +{
+  "default": "compact",
+  "description": "Compact model-selection output is the MCP default. Set view to full only when the complete OpenAI-compatible list shape is required.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. Changed3 schema fields changedv0.3.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / limit
      Removed value: -{
-  "default": 25,
-  "description": "Maximum number of models to return.",
-  "maximum": 100,
-  "minimum": 1,
-  "type": "integer"
-}
    • removedInput schema / properties / recommended_for
      Removed value: -{
-  "description": "Optional task filter such as image, video, embedding, or rerank.",
-  "enum": [
-    "image",
-    "video",
-    "music",
-    "3d",
-    "tts",
-    "stt",
-    "embedding",
-    "rerank",
-    "translation"
-  ],
-  "type": "string"
-}
  5. First observedv0.2.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, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds default-behavior context (native API calls default to full, integrations may default to compact) that isn't in the annotations, but says nothing about result volume, pagination, or how the two view shapes differ structurally.

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?

Four compact sentences, with the core purpose front-loaded and the parameter guidance following. No filler, though the default-behavior sentence is slightly tangential to the primary listing action.

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 5-parameter list tool with no output schema, the description covers view and recommended_for but is silent on the tag, category, and provider filters and on what the returned list contains. The schema carries those filters, so an agent can still call it, but the description is not fully self-sufficient.

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%, so the baseline is 3, but the description goes further by explaining the intent behind view=compact (model selection) versus view=full (OpenAI-compatible discovery shape) and by surfacing recommended_for for non-chat recommendations. It adds real semantic value on top of the schema, though it says nothing about tag/category/provider filtering.

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?

The description opens with a specific verb+resource ("Lists the currently available models"), which is unambiguous. It does not, however, differentiate itself from sibling tools like get_model, compare_models, or get_model_pricing, so an agent must infer the boundary from names alone.

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?

It gives useful conditional guidance for one parameter ("Use view=compact for model selection and view=full for the OpenAI-compatible discovery shape"), which implies when each mode applies. But it never states when to choose this tool over get_model or compare_models, so overall routing guidance is only partial.

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