Skip to main content
Glama
Appsilon

TealFlowMCP

Official
by Appsilon
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

tealflow_agent_guidance

Read-onlyIdempotent

Retrieve essential agent guidance before any Teal app task. Provides step-by-step workflows, module constraints, and best practices for correct, complete solutions.

Instructions

Get comprehensive guidance for assisting users with Teal application development.

⚠️ IMPORTANT: This tool MUST be called FIRST whenever a user requests:

  • Creating a Teal application or Teal app

  • Adding Teal modules to an app

  • Building clinical trial analysis applications

  • Survival analysis, safety analysis, efficacy analysis, or any clinical data analysis

  • Working with Statistical Analysis Plans (SAP)

  • Understanding Teal modules or datasets

  • Any other Teal-related task

This tool provides the complete agent usage guide that includes:

  • Your role and responsibilities as a Teal assistant

  • Available MCP tools and when to use them

  • Step-by-step workflow guidance for common scenarios

  • Teal framework knowledge (modules, datasets, architecture)

  • Important module constraints and special cases

  • Development philosophy and R code style guidelines

  • Best practices for agent behavior

  • Example workflows for common tasks

The guidance ensures you:

  • Follow correct workflows for creating and modifying Teal apps

  • Use the right MCP tools in the right sequence

  • Verify dataset compatibility before suggesting modules

  • Generate properly structured R code

  • Provide complete, working solutions

  • Handle multi-step tasks with proper planning

Usage: Always retrieve this guidance at the start of any Teal-related conversation to ensure you have the latest best practices, workflows, and constraints.

Returns: str: Complete agent guidance document in markdown format with all necessary context, workflows, and best practices for assisting with Teal development.

Examples: User: "I need to create a survival analysis app" → First action: Call this tool to get guidance → Then follow the workflow in the guidance to assist the user

User: "Add a Kaplan-Meier module to my app"
→ First action: Call this tool to get guidance
→ Then use the appropriate MCP tools as directed in the guidance

User: "Help me implement analyses from my SAP"
→ First action: Call this tool to get guidance
→ Then follow the SAP workflow described in the guidance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, etc.), the description explains what the tool returns (a complete markdown guidance document) and its role in ensuring correct workflows, tool sequencing, dataset compatibility checks, and code generation. This adds substantial behavioral context without contradicting annotations.

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?

The description is lengthy but well-structured with clear sections, bullet points, and examples. It is front-loaded with the critical 'IMPORTANT' notice. Some redundancy exists (e.g., repeated emphasis on calling first across multiple sections), but each part adds value for such an important prerequisite tool.

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

Completeness5/5

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

The description fully covers the tool's role, triggers, expected content, return type, and example workflows. Given the output schema exists and the tool has no parameters, this description provides all necessary context for an agent to use it correctly as the initial step in Teal-related interactions.

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

Parameters4/5

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

The tool has no parameters, so the baseline is 4. The description correctly omits parameter details and instead focuses on the tool's output and usage, which is appropriate for a zero-parameter meta-guidance tool.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Get comprehensive guidance for assisting users with Teal application development.' It uses a specific verb and resource, and distinguishes itself from sibling tools by positioning itself as the mandatory first step for any Teal-related task.

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

Usage Guidelines5/5

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

The description explicitly says when to use the tool ('MUST be called FIRST whenever...') with a detailed list of triggering scenarios, and provides example user requests with corresponding first actions. It also instructs 'Always retrieve this guidance at the start of any Teal-related conversation', making usage guidance unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Appsilon/TealFlowMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server