Skip to main content
Glama
Sign In
Tealfabric MCP Server for Cursor

Tealfabric MCP Server for Cursor

Official
by tealfabric
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

tealfabric_create_integration

Create a new Tealfabric integration with a defined name and type, including optional connector, configuration, status, and AI-agent execution settings.

Instructions

Create a new integration.

Input Schema

NameRequiredDescriptionDefault
nameYesIntegration name
typeYesIntegration type
statusNo
is_activeNoWhether integration is enabled
descriptionNo
connector_idNo
configurationNoConnector configuration
connector_configurationNoAlias for configuration
executable_by_ai_agentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / configuration
      Added value: +{
+  "additionalProperties": {},
+  "description": "Connector configuration",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedInput schema / properties / connector_configuration
      Added value: +{
+  "additionalProperties": {},
+  "description": "Alias for configuration",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedInput schema / properties / executable_by_ai_agents
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / status / enum
      Added value: +[
+  "active",
+  "inactive",
+  "error",
+  "testing"
+]
    • addedInput schema / properties / type / enum
      Added value: +[
+  "api",
+  "webhook",
+  "message_queue",
+  "file_transfer",
+  "database",
+  "email",
+  "sms",
+  "other"
+]
  2. First observedv0.1.3

TDQS

D1.6/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses essentially nothing: no auth/permission requirements, no side effects, no uniqueness or validation behavior, no indication of what the response contains. For a 9-parameter mutating tool this is a serious gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with zero filler is technically concise and front-loaded, but here brevity is under-specification rather than efficiency. There is no wasted text, yet the sentence does not earn its place by conveying anything an agent could not infer from the name.

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

Completeness1/5

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

Given 9 parameters, two nested object parameters, no annotations, and no output schema, the description is far too thin to call this tool correctly. Nothing tells the agent how to populate configuration, whether connector_id is required in practice, or what a successful creation returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 56% (status, connector_id, connector_configuration, description, executable_by_ai_agents are undocumented), and the description adds no parameter meaning at all. It does not explain the configuration vs connector_configuration alias, the relationship between status and is_active, or the role of executable_by_ai_agents.

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

Purpose2/5

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

The description nearly restates the tool name: 'Create' + 'integration' is exactly what tealfabric_create_integration encodes. It gives no scope detail (what an integration comprises, what is required, how it relates to connectors) and does nothing to separate it from siblings like tealfabric_update_integration or tealfabric_create_webapp.

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

Usage Guidelines1/5

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

There is no guidance on when to use this versus tealfabric_update_integration, tealfabric_execute_integration, or the connector tools. No preconditions, no mention that a connector_id may be needed first, and no statement of what happens if an integration with the same name already exists.

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