Skip to main content
Glama
nobrainer-tech

langflow-mcp-server

by nobrainer-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agentic_assist

Request AI assistance to build or edit Langflow flow components, specifying flow ID and optional component, field, model, or session context.

Instructions

Request agentic assistance for building or editing a flow component.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flow_idYesFlow ID
providerNoOptional provider
field_nameNoOptional target field name
model_nameNoOptional model name
session_idNoOptional session ID
input_valueNoUser input/instruction (server-configured limit)
max_retriesNoOptional max retries (1-5)
component_idNoOptional target component ID
history_limitNoOptional assistant history limit (0-100)
iterations_limitNoMaximum assistant iterations (1-200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv4.12.2
    • changedInput schema / properties / component_id / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / field_name / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • addedInput schema / properties / history_limit
      Added value: +{
+  "description": "Optional assistant history limit (0-100)",
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • changedInput schema / properties / input_value / description
      Previous value: -"User input/instruction"New value: +"User input/instruction (server-configured limit)"
    • changedInput schema / properties / input_value / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • addedInput schema / properties / iterations_limit
      Added value: +{
+  "description": "Maximum assistant iterations (1-200)",
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • changedInput schema / properties / max_retries / description
      Previous value: -"Optional max retries"New value: +"Optional max retries (1-5)"
    • changedInput schema / properties / max_retries / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedInput schema / properties / model_name / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / provider / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / session_id / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. First observedv4.11.0

TDQS

C2.6/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-disclosure burden. 'Building or editing' implies mutation, but the description does not disclose permissions required, side effects, reversibility, cost, non-determinism, or rate limits.

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 with no filler or repetition. It is efficiently sized, though for a 10-parameter agentic tool it risks being under-specified rather than optimally concise.

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?

The tool has 10 parameters (including session_id, model_name, max_retries, history_limit, iterations_limit), no annotations, and no output schema. The description does not explain session reuse, retry/iteration limits, expected return behavior, or how optional parameters affect the request, leaving substantial gaps.

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%, so the schema already documents all 10 parameters. The description mentions 'flow component', which loosely aligns with flow_id and component_id, but adds no syntax, format, or usage detail beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a high-level purpose ('Request agentic assistance for building or editing a flow component') but 'agentic assistance' is vague and does not distinguish this tool from siblings like agentic_assist_stream, agentic_assist_run, or agentic_execute. It identifies the resource area (flow component) but not the specific operation or output.

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?

No guidance on when to use this tool versus alternatives such as agentic_execute or agentic_assist_stream. There are no exclusions, prerequisites, or contextual conditions provided.

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