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_list_webapps

Retrieve and filter Tealfabric webapps for the authenticated tenant by name, type, process, or published status, with sorting and pagination.

Instructions

List Tealfabric webapps for the authenticated tenant.

Input Schema

NameRequiredDescriptionDefault
pageNo
typeNo
searchNoSearch by name or description
sort_byNo
process_idNo
items_per_pageNo
published_onlyNo
sort_directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / items_per_page
      Added value: +{
+  "anyOf": [
+    {
+      "const": 10,
+      "type": "number"
+    },
+    {
+      "const": 25,
+      "type": "number"
+    },
+    {
+      "const": 50,
+      "type": "number"
+    },
+    {
+      "const": 100,
+      "type": "number"
+    }
+  ]
+}
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "Max results (default 50)",
-  "type": "number"
-}
    • addedInput schema / properties / page
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / process_id
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / published_only
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / sort_by
      Added value: +{
+  "enum": [
+    "name",
+    "type",
+    "created_at",
+    "updated_at",
+    "version"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / sort_direction
      Added value: +{
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "type": "string"
+}
  2. First observedv0.1.3

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses tenant scoping (useful), but says nothing about pagination defaults, sort defaults, whether unpublished apps are included, result shape, or read-only safety. For an 8-parameter listing endpoint this is a notable 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?

One sentence, front-loaded and free of filler. However, the brevity reflects under-specification rather than disciplined economy given the tool's complexity.

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?

A listing tool with 8 optional filters, no annotations, no output schema, and almost no schema descriptions needs the description to explain filtering, sorting, and pagination behavior. None of that is present, leaving the agent to guess.

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

Parameters1/5

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

Schema coverage is only 13% (just 'search'), leaving page, type, sort_by, process_id, items_per_page, published_only, and sort_direction undocumented. The description adds no parameter meaning whatsoever, failing to compensate for the schema gap.

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?

Clear verb+resource ('List Tealfabric webapps') and scope ('for the authenticated tenant'). It does not distinguish itself from siblings like tealfabric_get_webapp or explain when a listing is preferable to fetching a single app, keeping it below a 5.

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?

There is no guidance on when to use this tool versus tealfabric_get_webapp, nor on how to use the filters or pagination. Usage is only implied by the verb 'List'.

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