Retrieve the mapping between model providers and their required global variables for Langflow workflows. Use it to find which variables to configure or use for each provider.
Get the mapping between model providers and their required global variables.
| Name | Required | Description | Default |
|---|---|---|---|
| purpose | No | Optional provider visibility purpose |
Changes observed during successful MCP inspections.
v4.12.2Input schema / properties / purposeAdded value: +{
+ "description": "Optional provider visibility purpose",
+ "enum": [
+ "use",
+ "configure"
+ ],
+ "type": "string"
+}v4.11.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It implies a read (Get) but never states that it is safe/non-mutating, what scope it returns (all providers? current project?), or what permissions are needed. The vague 'visibility purpose' concept motivating the parameter is also left unexplained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than crisp conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a small read-only getter with one optional parameter and no output schema, a minimal description is defensible. Still, it omits what the returned mapping actually contains and how the purpose enum affects results, leaving the agent guessing at the tool's output and the parameter's effect.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single optional 'purpose' parameter, so baseline is 3. The description adds no meaning beyond the schema and does not clarify the use/configure enum semantics, but it is not required to when the schema is fully documented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get) and resource (mapping between model providers and their required global variables), which is discernible from the name alone. However, it does not differentiate itself from nearby siblings like list_variables, list_model_providers, or list_model_provider_descriptors, so the agent must infer the distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use or when-not-to-use guidance is provided. The 'purpose' enum values (use vs configure) hint that there are distinct visibility scenarios, but the description never explains when to pick this tool over list_variables or the model-provider listing tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.