Skip to main content
Glama
nobrainer-tech

langflow-mcp-server

by nobrainer-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_models

Retrieve available models and filter them by provider, name, type, capabilities, or search query to find the right model.

Instructions

List available models with optional filters (provider, name, type, capabilities, search).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoSearch query
purposeNoOptional provider visibility purpose
providerNoFilter by provider
reasoningNoFilter to reasoning models
model_nameNoFilter by model name
model_typeNoFilter by model type
tool_callingNoFilter to tool-calling models
include_deprecatedNoInclude deprecated models
include_unsupportedNoInclude unsupported models

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.12.2
    • addedInput schema / properties / purpose
      Added value: +{
+  "description": "Optional provider visibility purpose",
+  "enum": [
+    "use",
+    "configure"
+  ],
+  "type": "string"
+}
  2. First observedv4.11.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether deprecated or unsupported models are excluded by default (a real ambiguity given the include_deprecated/include_unsupported flags), nor return format, ordering, or pagination behavior.

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 front-loaded sentence that names the resource and the filter categories with zero filler. It is appropriately sized, though the brevity contributes to the gaps noted elsewhere.

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

Completeness2/5

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

For a nine-parameter tool with no annotations and no output schema, the description is too thin. It omits default filtering behavior (deprecated/unsupported visibility) and the meaning of the 'purpose' enum, which an agent needs to call it correctly.

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 coverage is 100%, so the schema already documents all nine parameters, and the baseline of 3 applies. The parenthetical list (provider, name, type, capabilities, search) loosely maps to some parameters but adds no format, syntax, or default-value detail beyond what the schema provides.

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 and resource ('List available models') and notes the filtering capability. However, it does not differentiate itself from closely related siblings such as list_enabled_models, list_model_providers, or list_enabled_providers, leaving the agent to infer scope from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions optional filters but gives no guidance on when to use this tool versus list_enabled_models or list_model_providers, and no prerequisites or exclusions are stated. An agent has no basis for choosing among the several model-listing siblings.

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