universal-mcp-applications 0.1.18__py3-none-any.whl → 0.1.20__py3-none-any.whl

universal_mcp/applications/crustdata/README.md

@@ -1,10 +1,10 @@
-# Crustdata MCP Server
+# CrustdataApp MCP Server
 
-An MCP Server for the Crustdata API.
+An MCP Server for the CrustdataApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the Crustdata API.
+This is automatically generated from OpenAPI schema for the CrustdataApp API.
 
 
 | Tool | Description |

universal_mcp/applications/domain_checker/README.md

@@ -9,5 +9,5 @@ This is automatically generated from OpenAPI schema for the DomainCheckerApp API
 
 | Tool | Description |
 |------|-------------|
-| `check_domain_tool` | Checks if a domain is available for registration by querying DNS records and RDAP data. |
-| `check_tlds_tool` | Checks a keyword across multiple top-level domains (TLDs) to find available domain names. |
+| `check_domain_registration` | Determines a domain's availability by querying DNS and RDAP servers. For registered domains, it returns details like registrar and key dates. This function provides a comprehensive analysis for a single, fully qualified domain name, unlike `check_keyword_across_tlds_tool` which checks a keyword across multiple domains. |
+| `find_available_domains_for_keyword` | Checks a keyword's availability across a predefined list of popular TLDs. Using DNS and RDAP lookups, it generates a summary report of available and taken domains. This bulk-check differs from `check_domain_registration`, which deeply analyzes a single, fully-qualified domain. |

universal_mcp/applications/e2b/README.md

@@ -1,12 +1,12 @@
-# E2b MCP Server
+# E2bApp MCP Server
 
-An MCP Server for the E2b API.
+An MCP Server for the E2bApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the E2b API.
+This is automatically generated from OpenAPI schema for the E2bApp API.
 
 
 | Tool | Description |
 |------|-------------|
-| `execute_python_code` | Executes Python code in a sandbox environment and returns the formatted output |
+| `execute_python_code` | Executes a Python code string in a secure E2B sandbox. It authenticates using the configured API key, runs the code, and returns a formatted string containing the execution's output (stdout/stderr). It raises specific exceptions for authorization failures or general execution issues. |

universal_mcp/applications/elevenlabs/README.md

@@ -9,80 +9,6 @@ This is automatically generated from OpenAPI schema for the ElevenlabsApp API.
 
 | Tool | Description |
 |------|-------------|
-| `get_generated_items` | Retrieves historical data based on specified parameters, including page size and voice ID, using the "GET" method at the "/v1/history" endpoint. |
-| `get_history_item_by_id` | Retrieves a specific history item by its identifier using the API defined at "/v1/history/{history_item_id}" with the GET method. |
-| `delete_history_item` | Deletes a specific history item identified by its ID using the DELETE method. |
-| `get_audio_from_history_item` | Retrieves audio data for a specific history item identified by `{history_item_id}` using the `GET` method at the `/v1/history/{history_item_id}/audio` endpoint. |
-| `download_history_items` | Initiates a historical data download process and returns a success status upon completion. |
-| `delete_sample` | Deletes a specific voice sample identified by the `sample_id` from a voice with the given `voice_id` using the DELETE method. |
-| `get_audio_from_sample` | Retrieves the audio file for a specific sample associated with a given voice using the specified voice_id and sample_id. |
-| `convert` | Converts text into speech using a specified voice, allowing for optimization of streaming latency and selection of output format. |
-| `text_to_speech_with_timestamps` | Generates speech from text with precise character or word-level timing information using the specified voice, supporting audio-text synchronization through timestamps. |
-| `convert_as_stream` | Converts text to speech stream using the specified voice ID with configurable latency and output format. |
-| `stream_text_with_timestamps` | Converts text to speech using the specified voice ID, streaming the audio output with timestamps. |
-| `voice_generation_parameters` | Retrieves the parameters required for generating voice using the specified API endpoint. |
-| `generate_arandom_voice` | Generates an audio file by converting text into speech using a specified voice, allowing for customizable voice selection and text input. |
-| `create_voice_model` | Generates a custom voice using the provided parameters via the "/v1/voice-generation/create-voice" endpoint by sending a POST request, allowing users to create unique voice models. |
-| `create_previews` | Generates a voice preview from a given text prompt using the ElevenLabs API. |
-| `create_voice_from_preview` | Creates a new voice entry in the voice library using a generated preview ID and returns voice details. |
-| `get_user_subscription_info` | Retrieves the user's subscription details from the API. |
-| `get_user_info` | Retrieves user information from the API. |
-| `get_voices` | Retrieves a list of voices using the "GET" method at the "/v1/voices" API endpoint. |
-| `get_default_voice_settings` | Retrieves the default voice settings using the "GET" method at the "/v1/voices/settings/default" endpoint. |
-| `get_voice_settings` | Retrieves voice settings for a specific voice identified by `{voice_id}` using the "GET" method, returning the current configuration for that voice. |
-| `get_voice` | Retrieves the details of a specific voice by its ID using the "GET" method at the "/v1/voices/{voice_id}" endpoint. |
-| `delete_voice` | Deletes a voice with the specified ID using the DELETE method at the "/v1/voices/{voice_id}" endpoint. |
-| `edit_voice_settings` | Updates voice settings for a specified voice ID and returns a success status. |
-| `add_voice` | Adds a new voice entry to the voices collection using the provided data. |
-| `edit_voice` | Updates the specified voice by ID using a POST request and returns a success status upon completion. |
-| `add_sharing_voice` | Adds a voice associated with a public user ID and voice ID using the specified API endpoint. |
-| `get_shared_voices` | Retrieves a list of shared voices filtered by parameters like gender and language, with pagination support via page_size. |
-| `get_similar_library_voices` | Generates a list of similar voices using the POST method at the "/v1/similar-voices" endpoint. |
-| `get_aprofile_page` | Retrieves a unified customer profile by handle and returns the associated attributes, identifiers, and traits. |
-| `get_projects` | Retrieves a list of projects using the API defined at the "/v1/projects" endpoint via the GET method. |
-| `add_project` | Creates a new project and returns a status message. |
-| `get_project_by_id` | Retrieves information for a specific project identified by `{project_id}` using the API endpoint at "/v1/projects/{project_id}" via the GET method. |
-| `edit_basic_project_info` | Creates a new project resource by sending data to the specified project identifier using the POST method at the "/v1/projects/{project_id}" endpoint. |
-| `delete_project` | Deletes the specified project and returns a success status upon completion. |
-| `convert_project` | Converts a specified project identified by project_id and returns the conversion result. |
-| `get_project_snapshots` | Retrieves a list of snapshots associated with a specified project. |
-| `streams_archive_with_project_audio` | Archives a project snapshot using the specified project ID and snapshot ID and returns a success status. |
-| `add_chapter_to_aproject` | Adds a new chapter to a specified project using the provided project identifier and returns a success status upon completion. |
-| `update_project_pronunciations` | Updates pronunciation dictionaries for a specified project using the POST method, returning a successful status message upon completion. |
-| `get_chapters` | Retrieves a chapter for a specified project by ID using the GET method. |
-| `get_chapter_by_id` | Retrieves a specific chapter within a project identified by project_id and chapter_id. |
-| `delete_chapter` | Deletes a specific chapter within a project using the "DELETE" method. |
-| `convert_chapter` | Converts a chapter in a project using the POST method and returns a response upon successful conversion. |
-| `get_chapter_snapshots` | Retrieves a snapshot for a specific chapter within a project using the provided project and chapter IDs. |
-| `stream_chapter_audio` | Streams data from a specific chapter snapshot in a project using the API and returns a response indicating success. |
-| `dub_avideo_or_an_audio_file` | Initiates a dubbing process and returns a status message using the API defined at the "/v1/dubbing" endpoint via the POST method. |
-| `get_dubbing_project_metadata` | Retrieves the details of a specific dubbing job using the provided dubbing ID. |
-| `delete_dubbing_project` | Deletes a dubbing project with the specified ID and returns a success status upon completion. |
-| `get_transcript_for_dub` | Retrieves the transcript for a specific dubbing task in the requested language using the "GET" method. |
-| `get_models` | Retrieves a list of models using the GET method at the "/v1/models" endpoint. |
-| `post_audio_native` | Processes audio data using the audio-native API and returns a response. |
-| `get_characters_usage_metrics` | Retrieves character statistics within a specified time frame using the start and end Unix timestamps provided in the query parameters. |
-| `add_apronunciation_dictionary` | Creates a pronunciation dictionary from a lexicon file and returns its ID and metadata. |
-| `add_rules_to_dictionary` | Adds pronunciation rules to a specific pronunciation dictionary identified by its ID using the POST method. |
-| `remove_pronunciation_rules` | Removes specified pronunciation rules from a pronunciation dictionary using a POST request. |
-| `get_dictionary_version_file` | Retrieves and downloads a specific version of a pronunciation dictionary file using its dictionary ID and version ID. |
-| `get_pronunciation_dictionary` | Retrieves a specific pronunciation dictionary by its ID using the "GET" method from the "/v1/pronunciation-dictionaries/{pronunciation_dictionary_id}" endpoint. |
-| `get_pronunciation_dictionaries` | Retrieves a list of pronunciation dictionaries using the GET method at the "/v1/pronunciation-dictionaries" endpoint, allowing users to specify the number of items per page via the "page_size" query parameter. |
-| `invite_user` | Invites a user to join a workspace by sending an invitation, allowing them to access the specified workspace upon acceptance. |
-| `delete_existing_invitation` | Deletes a workspace invite and returns a success response upon completion. |
-| `update_member` | Adds members to a workspace and returns the updated member list upon success. |
-| `get_signed_url` | Generates a signed URL for initiating a conversation with a specific conversational AI agent, identified by the provided `agent_id`, using the ElevenLabs API. |
-| `create_agent` | Creates a conversational AI agent with specified configuration settings and returns the agent details. |
-| `get_agent` | Retrieves information about a specific conversational AI agent by its unique identifier using the GET method at the "/v1/convai/agents/{agent_id}" API endpoint. |
-| `delete_agent` | Deletes a specified Conversational AI agent using the DELETE method. |
-| `patches_an_agent_settings` | Updates an existing conversational AI agent's settings using the specified agent ID, allowing changes to properties such as the agent's name and tool configurations. |
-| `get_agent_widget_config` | Retrieves and configures the Convai widget for the specified agent, but the provided details do not specify the exact functionality of this specific endpoint, suggesting it may relate to integrating or customizing Convai's character interaction capabilities. |
-| `get_shareable_agent_link` | Retrieves and establishes a link for a Convai agent using the specified agent ID, facilitating integration or connectivity operations. |
-| `post_agent_avatar` | Creates and configures a Convai avatar for a specific agent using the POST method, though the exact details of this endpoint are not provided in the available documentation. |
-| `get_agent_knowledge_base` | Retrieves specific documentation for a knowledge base associated with an agent in Convai. |
-| `add_agent_secret` | Adds a secret to a specified conversational AI agent through the API and returns a status confirmation. |
-| `add_to_agent_sknowledge_base` | Adds new content to an agent's knowledge base by uploading a file or resource, which can be used to enhance the agent's conversational capabilities. |
-| `get_agents_page` | Retrieves a list of conversational AI agents available in the Convai system. |
-| `get_conversations` | Retrieves conversation history for a specified agent ID. |
-| `get_conversation_details` | Retrieves and formats the details of a specific conversation based on the provided conversation ID. |
-| `get_conversation_audio` | Retrieves the audio from a specific conversation using the ElevenLabs Conversational AI API. |
+| `generate_speech_audio_url` | Converts a text string into speech using the ElevenLabs API. The function then saves the generated audio to a temporary MP3 file and returns a public URL to access it, rather than the raw audio bytes. |
+| `speech_to_text` | Transcribes an audio file into text using the ElevenLabs API. It supports language specification and speaker diarization, providing the inverse operation to the audio-generating `text_to_speech` method. Note: The docstring indicates this is a placeholder for an undocumented endpoint. |
+| `speech_to_speech` | Downloads an audio file from a URL and converts the speech into a specified target voice using the ElevenLabs API. This function transforms the speaker's voice in an existing recording and returns the new audio data as bytes, distinct from creating audio from text. |

universal_mcp/applications/exa/README.md

@@ -1,15 +1,15 @@
-# Exa MCP Server
+# ExaApp MCP Server
 
-An MCP Server for the Exa API.
+An MCP Server for the ExaApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the Exa API.
+This is automatically generated from OpenAPI schema for the ExaApp API.
 
 
 | Tool | Description |
 |------|-------------|
-| `search` | Searches for data using the specified criteria and returns a list of results. |
-| `find_similar` | Finds and returns similar items using the API at "/findSimilar" via the POST method. |
-| `get_contents` | Creates new content entries via a POST request to the "/contents" endpoint. |
-| `answer` | Provides an answer to a query using the API endpoint at "/answer" via the POST method. |
+| `search_with_filters` | Executes a query against the Exa API's `/search` endpoint, returning a list of results. This function supports extensive filtering by search type, category, domains, publication dates, and specific text content to refine the search query and tailor the API's response. |
+| `find_similar_by_url` | Finds web pages semantically similar to a given URL. Unlike the `search` function, which uses a text query, this method takes a specific link and returns a list of related results, with options to filter by domain, publication date, and content. |
+| `fetch_page_content` | Retrieves and processes content from a list of URLs, returning full text, summaries, or highlights. Unlike the search function which finds links, this function fetches the actual page content, with optional support for live crawling to get the most up-to-date information. |
+| `answer` | Retrieves a direct, synthesized answer for a given query by calling the Exa `/answer` API endpoint. Unlike `search`, which returns web results, this function provides a conclusive response. It supports streaming, including source text, and selecting a search model. |

universal_mcp/applications/falai/README.md

@@ -1,17 +1,18 @@
-# Falai MCP Server
+# FalaiApp MCP Server
 
-An MCP Server for the Falai API.
+An MCP Server for the FalaiApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the Falai API.
+This is automatically generated from OpenAPI schema for the FalaiApp API.
 
-| Tool             | Description                                                                                                                                                  |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `run`            | Run a Fal AI application directly and wait for the result. Suitable for short-running applications with synchronous execution from the caller's perspective. |
-| `submit`         | Submits a request to the Fal AI queue for asynchronous processing and returns a request ID for tracking the job.                                             |
-| `status`         | Checks the status of a previously submitted Fal AI request and retrieves its current execution state                                                         |
-| `result`         | Retrieves the result of a completed Fal AI request, waiting for completion if the request is still running.                                                  |
-| `cancel`         | Asynchronously cancels a running or queued Fal AI request.                                                                                                   |
-| `upload_file`    | Uploads a local file to the Fal CDN and returns its public URL                                                                                               |
-| `generate_image` | Asynchronously generates images using the 'fal-ai/flux/dev' application with customizable parameters and default settings                                    |
+
+| Tool | Description |
+|------|-------------|
+| `run` | Executes a Fal AI application synchronously, waiting for completion and returning the result directly. This method is suited for short-running tasks, unlike `submit` which queues a job for asynchronous processing and returns a request ID instead of the final output. |
+| `submit` | Submits a job to the Fal AI queue for asynchronous processing, immediately returning a request ID. This contrasts with the `run` method, which waits for completion. The returned ID is used by `check_status`, `get_result`, and `cancel` to manage the job's lifecycle. |
+| `check_status` | Checks the execution state (e.g., Queued, InProgress) of an asynchronous Fal AI job using its request ID. It provides a non-blocking way to monitor jobs initiated via `submit` without fetching the final `result`, and can optionally include logs. |
+| `get_result` | Retrieves the final result of an asynchronous job, identified by its `request_id`. This function waits for the job, initiated via `submit`, to complete. Unlike the non-blocking `check_status`, this method blocks execution to fetch and return the job's actual output upon completion. |
+| `cancel` | Asynchronously cancels a running or queued Fal AI job using its `request_id`. This function complements the `submit` method, providing a way to terminate asynchronous tasks before completion. It raises a `ToolError` if the cancellation request fails. |
+| `upload_file` | Asynchronously uploads a local file to the Fal Content Delivery Network (CDN), returning a public URL. This URL makes the file accessible for use as input in other Fal AI job execution methods like `run` or `submit`. A `ToolError` is raised if the upload fails. |
+| `run_image_generation` | A specialized wrapper for the `run` method that synchronously generates images using the 'fal-ai/flux/dev' model. It simplifies image creation with common parameters like `prompt` and `seed`, waits for the task to complete, and directly returns the result containing image URLs and metadata. |

universal_mcp/applications/figma/README.md

@@ -1,10 +1,10 @@
-# Figma MCP Server
+# FigmaApp MCP Server
 
-An MCP Server for the Figma API.
+An MCP Server for the FigmaApp API.
 
 ## 🛠️ Tool List
 
-This is automatically generated from OpenAPI schema for the Figma API.
+This is automatically generated from OpenAPI schema for the FigmaApp API.
 
 
 | Tool | Description |

universal_mcp/applications/file_system/README.md

@@ -0,0 +1,13 @@
+# FileSystemApp MCP Server
+
+An MCP Server for the FileSystemApp API.
+
+## 🛠️ Tool List
+
+This is automatically generated from OpenAPI schema for the FileSystemApp API.
+
+
+| Tool | Description |
+|------|-------------|
+| `read_file` | Asynchronously reads the entire content of a specified file in binary mode. This static method takes a file path and returns its data as a bytes object, serving as a fundamental file retrieval operation within the FileSystem application. |
+| `write_file` | Writes binary data to a specified file path. If no path is provided, it creates a unique temporary file in `/tmp`. The function returns a dictionary confirming success and providing metadata about the new file, including its path and size. |

universal_mcp/applications/firecrawl/README.md

@@ -9,12 +9,12 @@ This is automatically generated from OpenAPI schema for the FirecrawlApp API.
 
 | Tool | Description |
 |------|-------------|
-| `scrape_url` | Scrapes a single URL using Firecrawl and returns the extracted data. |
-| `search` | Performs a web search using Firecrawl's search capability. |
-| `start_crawl` | Starts a async crawl job for a given URL using Firecrawl. Returns the job ID immediately. |
-| `check_crawl_status` | Checks the status of a previously initiated async Firecrawl crawl job. |
-| `cancel_crawl` | Cancels a currently running Firecrawl crawl job. |
-| `start_batch_scrape` | Starts a batch scrape job for multiple URLs using Firecrawl. (Note: May map to multiple individual scrapes or a specific batch API endpoint if available) |
-| `check_batch_scrape_status` | Checks the status of a previously initiated Firecrawl batch scrape job. |
-| `quick_web_extract` | Performs a quick, synchronous extraction of data from one or more URLs using Firecrawl and returns the results directly. |
-| `check_extract_status` | Checks the status of a previously initiated Firecrawl extraction job. |
+| `scrape_url` | Synchronously scrapes a single URL, immediately returning its content. This provides a direct method for single-page scraping, contrasting with asynchronous, job-based functions like `start_crawl` (for entire sites) and `start_batch_scrape` (for multiple URLs). |
+| `search` | Executes a synchronous web search using the Firecrawl service for a given query. Unlike scrape_url which fetches a single page, this function discovers web content. It returns a dictionary of results on success or an error string on failure, raising exceptions for authorization or SDK issues. |
+| `start_crawl` | Starts an asynchronous Firecrawl job to crawl a website from a given URL, returning a job ID. Unlike the synchronous `scrape_url` for single pages, this function initiates a comprehensive, link-following crawl. Progress can be monitored using the `check_crawl_status` function with the returned ID. |
+| `check_crawl_status` | Retrieves the status of an asynchronous Firecrawl job using its unique ID. As the counterpart to `start_crawl`, this function exclusively monitors website crawl progress, distinct from status checkers for batch scraping or data extraction jobs. Returns job details on success or an error message on failure. |
+| `cancel_crawl` | Cancels a running asynchronous Firecrawl crawl job using its unique ID. As a lifecycle management tool for jobs initiated by `start_crawl`, it returns a confirmation status upon success or an error message on failure, distinguishing it from controls for other job types. |
+| `start_batch_scrape` | Initiates an asynchronous Firecrawl job to scrape a list of URLs. It returns a job ID for tracking with `check_batch_scrape_status`. Unlike the synchronous `scrape_url` which processes a single URL, this function handles bulk scraping and doesn't wait for completion. |
+| `check_batch_scrape_status` | Checks the status of an asynchronous batch scrape job using its job ID. As the counterpart to `start_batch_scrape`, it specifically monitors multi-URL scraping tasks, distinct from checkers for site-wide crawls (`check_crawl_status`) or AI-driven extractions (`check_extract_status`). Returns detailed progress or an error message. |
+| `quick_web_extract` | Performs synchronous, AI-driven data extraction from URLs using an optional prompt or schema. Unlike asynchronous jobs like `start_crawl`, it returns structured data directly. This function raises an exception on failure, contrasting with other methods in the class that return an error string upon failure. |
+| `check_extract_status` | Checks the status of an asynchronous, AI-powered Firecrawl data extraction job using its ID. Unlike `check_crawl_status` or `check_batch_scrape_status`, this function specifically monitors structured data extraction tasks, returning the job's progress or an error message on failure. |

universal_mcp/applications/fireflies/README.md

@@ -9,17 +9,17 @@ This is automatically generated from OpenAPI schema for the FirefliesApp API.
 
 | Tool | Description |
 |------|-------------|
-| `get_team_analytics` | Fetches team analytics data within a specified time range. |
-| `get_ai_apps_outputs` | Fetches AI Apps outputs for a given transcript. |
-| `get_user_details` | Fetches details for a specific user. |
-| `list_users` | Fetches a list of users in the workspace. |
-| `get_transcript_details` | Fetches details for a specific transcript. |
-| `list_transcripts` | Fetches a list of transcripts, optionally filtered by user ID. |
-| `get_bite_details` | Fetches details for a specific bite (soundbite/clip). |
-| `list_bites` | Fetches a list of bites, optionally filtered to the current user's bites. |
-| `add_to_live_meeting` | Adds Fireflies.ai to a live meeting. |
-| `create_bite` | Creates a bite (soundbite/clip) from a transcript. |
-| `delete_transcript` | Deletes a transcript. |
-| `set_user_role` | Sets the role for a user. |
-| `upload_audio` | Uploads an audio file for transcription. |
-| `update_meeting_title` | Updates the title of a meeting (transcript). |
+| `get_team_conversation_analytics` | Queries the Fireflies.ai API for team conversation analytics, specifically the average number of filler words. The data retrieval can optionally be filtered by a start and end time. Returns a dictionary containing the fetched analytics. |
+| `get_transcript_ai_outputs` | Retrieves all AI-generated application outputs, such as summaries or analyses, associated with a specific transcript ID. It fetches the detailed prompt and response data for each AI app that has processed the transcript, providing a complete record of AI-generated content. |
+| `get_user_details` | Fetches details, such as name and integrations, for a single user identified by their unique ID. This function queries for a specific user, differentiating it from `list_users` which retrieves a list of all users in the workspace. |
+| `list_users` | Retrieves a list of all users in the workspace, returning each user's name and configured integrations. It provides a complete team roster, differing from `get_user_details`, which fetches information for a single user by their ID. |
+| `get_transcript_details` | Queries the Fireflies API for a single transcript's details, such as title and ID, using its unique identifier. It fetches one specific entry, distinguishing it from `list_transcripts`, which retrieves a collection, and from `get_ai_apps_outputs` which gets AI data from a transcript. |
+| `list_transcripts` | Fetches a list of meeting transcripts, returning the title and ID for each. The list can be filtered to return only transcripts for a specific user. This function complements `get_transcript_details`, which retrieves a single transcript by its unique ID. |
+| `get_bite_details` | Retrieves detailed information for a specific bite (soundbite/clip) using its unique ID. It fetches data including the user ID, name, processing status, and summary. This provides a focused view of a single bite, distinguishing it from `list_bites` which fetches a collection of bites. |
+| `list_bites` | Retrieves a list of soundbites (clips) from the Fireflies API. An optional 'mine' parameter filters for soundbites belonging only to the authenticated user. Differentiates from 'get_bite_details' by fetching multiple items rather than a single one by ID. |
+| `add_to_live_meeting` | Executes a GraphQL mutation to make the Fireflies.ai notetaker join a live meeting specified by its URL. This action initiates the bot's recording and transcription process for the ongoing session and returns a success confirmation. |
+| `create_soundbite_from_transcript` | Creates a soundbite/clip from a specified segment of a transcript using its ID, start, and end times. This function executes a GraphQL mutation, returning details of the newly created bite, such as its ID and processing status. |
+| `delete_transcript` | Permanently deletes a specific transcript from Fireflies.ai using its ID. This destructive operation executes a GraphQL mutation and returns a dictionary containing the details of the transcript (e.g., title, date) as it existed just before being removed, confirming the action. |
+| `set_user_role` | Assigns a new role (e.g., 'admin', 'member') to a user specified by their ID. This function executes a GraphQL mutation to modify user data and returns a dictionary with the user's updated name and admin status to confirm the change. |
+| `transcribe_audio_from_url` | Submits an audio file from a URL to the Fireflies.ai API for transcription. It can optionally associate a title and a list of attendees with the audio, returning the upload status and details upon completion. |
+| `update_transcript_title` | Updates the title of a specific transcript, identified by its ID, to a new value. This function executes a GraphQL mutation and returns a dictionary containing the newly assigned title upon successful completion of the request. |

universal_mcp/applications/fireflies/app.py

@@ -175,8 +175,116 @@ class FirefliesApp(GraphQLApplication):
         query_gql = gql("""
         query Transcript($transcriptId: String!) {
           transcript(id: $transcriptId) {
-            title
             id
+            title
+            host_email
+            organizer_email
+            user {
+              user_id
+              email
+              name
+              num_transcripts
+              recent_meeting
+              minutes_consumed
+              is_admin
+              integrations
+            }
+            speakers {
+              id
+              name
+            }
+            transcript_url
+            participants
+            meeting_attendees {
+              displayName
+              email
+              phoneNumber
+              name
+              location
+            }
+            fireflies_users
+            duration
+            dateString
+            date
+            audio_url
+            video_url
+            sentences {
+              index
+              speaker_name
+              speaker_id
+              text
+              raw_text
+              start_time
+              end_time
+              ai_filters {
+                task
+                pricing
+                metric
+                question
+                date_and_time
+                text_cleanup
+                sentiment
+              }
+            }
+            calendar_id
+            summary {
+              action_items
+              keywords
+              outline
+              overview
+              shorthand_bullet
+              gist
+              bullet_gist
+              short_summary
+              short_overview
+              meeting_type
+              topics_discussed
+              transcript_chapters
+            }
+            meeting_info {
+              fred_joined
+              silent_meeting
+              summary_status
+            }
+            cal_id
+            calendar_type
+            apps_preview {
+              outputs {
+                transcript_id
+                user_id
+                app_id
+                created_at
+                title
+                prompt
+                response
+              }
+            }
+            meeting_link
+            analytics {
+              sentiments {
+                negative_pct
+                neutral_pct
+                positive_pct
+              }
+              categories {
+                questions
+                date_times
+                metrics
+                tasks
+              }
+              speakers {
+                speaker_id
+                name
+                duration
+                word_count
+                longest_monologue
+                monologues_count
+                filler_words
+                questions
+                duration_pct
+                words_per_minute
+              }
+            }
           }
         }
         """)

universal_mcp/applications/fpl/README.md

@@ -9,15 +9,15 @@ This is automatically generated from OpenAPI schema for the FplApp API.
 
 | Tool | Description |
 |------|-------------|
-| `get_player_information` | Get detailed information and statistics for a specific player |
-| `search_fpl_players` | Search for FPL players by name with optional filtering |
-| `get_gameweek_status` | Get precise information about current, previous, and next gameweeks. |
-| `analyze_players` | Filter and analyze FPL players based on multiple criteria |
-| `compare_players` | Compare multiple players across various metrics |
-| `analyze_player_fixtures` | Analyze upcoming fixtures for a player and provide a difficulty rating |
-| `analyze_fixtures` | Analyze upcoming fixtures for players, teams, or positions |
-| `get_blank_gameweeks` | Get information about upcoming blank gameweeks where teams don't have fixtures |
-| `get_double_gameweeks` | Get information about upcoming double gameweeks where teams have multiple fixtures |
-| `get_league_standings` | Get standings for a specified FPL league |
-| `get_league_analytics` | Get rich analytics for a Fantasy Premier League mini-league |
-| `team_info` | Get information about a team  |
+| `get_player_information` | Fetches a detailed profile for a specific FPL player, identified by ID or name. It can include gameweek performance history, filterable by range, and future fixtures. This provides an in-depth look at one player, differing from broader search or analysis functions like `search_fpl_players`. |
+| `find_players` | Searches for FPL players by full or partial name with optional filtering by team and position. This is a discovery tool, differentiating it from `get_player_information` which fetches a specific known player. It serves as a public interface to the internal `search_players` utility. |
+| `get_gameweek_snapshot` | Provides a detailed snapshot of the FPL schedule by identifying the current, previous, and next gameweeks. It calculates the precise real-time status of the current gameweek (e.g., 'Imminent', 'In Progress') and returns key deadline times and overall season progress. |
+| `screen_players` | Filters the FPL player database using multiple criteria like position, price, points, and form. Returns a sorted list of matching players, summary statistics for the filtered group, and optional recent gameweek performance data to aid in player discovery and analysis. |
+| `compare_players` | Performs a detailed comparison of multiple players based on specified metrics, recent gameweek history, and upcoming fixture analysis. It provides a side-by-side breakdown, identifies the best performer per metric, and determines an overall winner, considering fixture difficulty, blanks, and doubles for a comprehensive overview. |
+| `analyze_player_fixtures` | Analyzes a player's upcoming fixture difficulty. Given a player's name, it retrieves their schedule for a set number of matches, returning a detailed list and a calculated difficulty rating. This method is a focused alternative to the more comprehensive `analyze_fixtures` function. |
+| `analyze_entity_fixtures` | Provides a detailed fixture difficulty analysis for a specific player, team, or an entire position over a set number of gameweeks. It calculates a difficulty score and can include blank/double gameweek data, offering broader analysis than the player-only `analyze_player_fixtures`. |
+| `get_blank_gameweeks` | Identifies upcoming 'blank' gameweeks where teams lack a scheduled fixture. The function returns a list detailing each blank gameweek and the affected teams within a specified number of weeks, which is essential for strategic planning. It is distinct from `get_double_gameweeks`. |
+| `get_double_gameweeks` | Identifies upcoming double gameweeks where teams have multiple fixtures within a specified number of weeks. It returns a list detailing each double gameweek and the teams involved. This function specifically finds gameweeks with extra matches, unlike `get_blank_gameweeks` which finds those with none. |
+| `get_league_standings` | Retrieves current standings for a specified FPL classic mini-league by its ID. It fetches and parses raw API data to provide a direct snapshot of the league table, distinguishing it from `get_league_analytics` which performs deeper, historical analysis. |
+| `analyze_league` | Performs advanced analysis on an FPL league for a given gameweek range. It routes requests based on the analysis type ('overview', 'historical', 'team_composition') to provide deeper insights beyond the basic rankings from `get_league_standings`, such as historical performance or team composition. |
+| `get_manager_team_info` | Retrieves detailed information for a specific FPL manager's team (an "entry") using its unique ID. This is distinct from functions analyzing Premier League clubs, as it targets an individual user's fantasy squad and its performance details within the game. |

universal_mcp/applications/fpl/app.py

@@ -7,8 +7,8 @@ import requests
 from universal_mcp.applications.application import APIApplication
 from universal_mcp.integrations import Integration
 
-from .utils.api import api
-from .utils.fixtures import (
+from universal_mcp.applications.fpl.utils.api import api
+from universal_mcp.applications.fpl.utils.fixtures import (
     analyze_player_fixtures,
     get_blank_gameweeks,
     get_double_gameweeks,
@@ -16,20 +16,20 @@ from .utils.fixtures import (
     get_player_fixtures,
     get_player_gameweek_history,
 )
-from .utils.helper import (
+from universal_mcp.applications.fpl.utils.helper import (
     find_players_by_name,
     get_player_info,
     get_players_resource,
     get_team_by_name,
     search_players,
 )
-from .utils.league_utils import (
+from universal_mcp.applications.fpl.utils.league_utils import (
     _get_league_historical_performance,
     _get_league_standings,
     _get_league_team_composition,
     parse_league_standings,
 )
-from .utils.position_utils import normalize_position
+from universal_mcp.applications.fpl.utils.position_utils import normalize_position
 
 
 class FplApp(APIApplication):

universal_mcp/applications/github/README.md

@@ -9,13 +9,13 @@ This is automatically generated from OpenAPI schema for the GithubApp API.
 
 | Tool | Description |
 |------|-------------|
-| `star_repository` | Stars a GitHub repository using the GitHub API and returns a status message. |
-| `list_commits` | Retrieves and formats a list of recent commits from a GitHub repository |
-| `list_branches` | Lists all branches for a specified GitHub repository and returns them in a formatted string representation. |
-| `list_pull_requests` | Retrieves and formats a list of pull requests for a specified GitHub repository. |
-| `list_issues` | Retrieves a list of issues from a specified GitHub repository with optional filtering parameters. |
-| `get_pull_request` | Retrieves and formats detailed information about a specific GitHub pull request from a repository |
-| `create_pull_request` | Creates a new pull request in a GitHub repository, optionally converting an existing issue into a pull request. |
-| `create_issue` | Creates a new issue in a specified GitHub repository with a title, body content, and optional labels. |
-| `update_issue` | Updates an existing GitHub issue with specified parameters including title, body, assignee, state, and state reason. |
-| `list_repo_activities` | Retrieves and formats a list of activities for a specified GitHub repository. |
+| `star_repository` | Stars a GitHub repository for the authenticated user. This user-centric action takes the full repository name ('owner/repo') and returns a simple string message confirming the outcome, unlike other functions that list or create repository content like issues or pull requests. |
+| `list_recent_commits` | Fetches and formats the 12 most recent commits from a repository. It returns a human-readable string summarizing each commit's hash, author, and message, providing a focused overview of recent code changes, unlike functions that list branches, issues, or pull requests. |
+| `list_branches` | Fetches all branches for a specified GitHub repository and formats them into a human-readable string. This method is distinct from others like `search_issues`, as it returns a formatted list for display rather than raw JSON data for programmatic use. |
+| `list_pull_requests` | Fetches pull requests for a repository, filtered by state (e.g., 'open'). It returns a formatted string summarizing each PR's details, distinguishing it from `get_pull_request` (single PR) and `search_issues` (raw issue data). |
+| `search_issues` | Fetches issues from a GitHub repository using specified filters (state, assignee, labels) and pagination. It returns the raw API response as a list of dictionaries, providing detailed issue data for programmatic processing, distinct from other methods that return formatted strings. |
+| `get_pull_request` | Fetches a specific pull request from a repository using its unique number. It returns a human-readable string summarizing the PR's title, creator, status, and description, unlike `list_pull_requests` which retrieves a list of multiple PRs. |
+| `create_pull_request` | Creates a pull request between specified `head` and `base` branches, or converts an issue into a PR. Unlike read functions that return formatted strings, this write operation returns the raw API response as a dictionary, providing comprehensive data on the newly created pull request. |
+| `create_issue` | Creates a new issue in a GitHub repository using a title, body, and optional labels. It returns a formatted confirmation string with the new issue's number and URL, differing from `update_issue` which modifies existing issues and `search_issues` which returns raw API data. |
+| `update_issue` | Modifies an existing GitHub issue, identified by its number within a repository. It can update optional fields like title, body, or state and returns the raw API response as a dictionary, differentiating it from `create_issue` which makes new issues and returns a formatted string. |
+| `list_repo_activities` | Fetches recent events for a GitHub repository and formats them into a human-readable string. It summarizes activities with actors and timestamps, providing a general event feed, unlike other `list_*` functions which retrieve specific resources like commits or issues. |

universal_mcp/applications/google_calendar/README.md

@@ -9,13 +9,13 @@ This is automatically generated from OpenAPI schema for the GoogleCalendarApp AP
 
 | Tool | Description |
 |------|-------------|
-| `get_event` | Retrieves detailed information about a specific Google Calendar event by its ID |
-| `get_today_events` | Retrieves events from Google Calendar for today or a specified number of future days. |
-| `list_events` | Retrieves a list of events from Google Calendar with customizable filtering, sorting, and pagination options |
-| `quick_add_event` | Creates a calendar event. Use it only when user specfies that they want to add a quick event |
-| `add_an_event` | Creates a new calendar event with details like start time, end time, summary, description, location, attendees, and recurrence rules. |
-| `update_event` | Updates an existing calendar event. This method updates the entire event resource. |
-| `get_event_instances` | Retrieves all instances of a recurring calendar event within a specified time range. |
-| `get_user_timezone` | Gets the user's calendar timezone setting to help with timezone-aware event creation. |
-| `delete_event` | Deletes an event from the specified calendar. |
-| `query_free_busy` | Checks if you have free slots or not by querying the free/busy status of your calendars. |
+| `get_event_by_id` | Retrieves a specific calendar event using its unique ID. Unlike `list_events`, which fetches multiple events based on date ranges or search queries, this function targets a single, known event. It can optionally limit attendees returned and specify a time zone for date formatting in the response. |
+| `get_upcoming_events` | Retrieves events for a specified number of days, starting from today. This function simplifies date-range queries by auto-calculating start/end times, unlike the more comprehensive `list_events` function, which offers granular control with explicit time filters, text search, and custom sorting. |
+| `list_events` | Fetches a customizable list of events using filters for date range, text search, sorting, and pagination. This advanced function provides more granular control than `get_upcoming_events`, which is limited to fetching events for a specific number of upcoming days. |
+| `create_event_from_text` | Creates a calendar event by parsing a natural language string (e.g., "Meeting tomorrow at 10am"). This offers a user-friendly shortcut, contrasting with the structured `create_event` function which requires explicit fields like start and end times. |
+| `create_event` | Creates a calendar event using structured data for start/end times, summary, attendees, and recurrence. This method provides precise control for complex appointments, unlike `create_event_from_text` which parses natural language, making it ideal for detailed or recurring event creation. |
+| `replace_event` | Replaces an existing calendar event, identified by its ID, with new data. This function performs a full update, overwriting all event properties like start/end times and summary. It does not support partial modifications, requiring all necessary fields for the replacement to be provided. |
+| `list_recurring_event_instances` | Retrieves all individual occurrences of a specific recurring event using its ID. Unlike `list_events`, which fetches multiple distinct events, this function expands a single recurring event into its separate instances, allowing filtering by time range and pagination for detailed scheduling views. |
+| `get_primary_calendar_details` | Retrieves metadata for the user's primary calendar, including its default timezone. This information is essential for creating new events with accurate, timezone-aware start and end times using other functions like `create_event`, preventing potential scheduling errors across different regions. |
+| `delete_event` | Permanently deletes a specific event from a Google Calendar using its event and calendar IDs. It can optionally send cancellation notifications to attendees, distinguishing it from functions that retrieve (`get_event_by_id`) or modify events (`replace_event`), which do not remove entries from the calendar. |
+| `get_free_busy_info` | Queries the free/busy status for one or more calendars within a specified time range. It returns a list of busy time intervals, making it ideal for finding open slots and scheduling new events without conflicts. |

universal_mcp/applications/google_docs/README.md

@@ -9,17 +9,17 @@ This is automatically generated from OpenAPI schema for the GoogleDocsApp API.
 
 | Tool | Description |
 |------|-------------|
-| `create_document` | Creates a new blank Google Document with the specified title and returns the API response. |
-| `get_document` | Retrieves the latest version of a specified document from the Google Docs API. |
-| `add_content` | Adds text content at a specified position in an existing Google Document via the Google Docs API. |
-| `style_text` | Simplified text styling for Google Document - handles most common cases. |
-| `delete_content` | Deletes content from a specified range in a Google Document. |
-| `insert_table` | Inserts a table at the specified location in a Google Document. |
-| `create_footer` | Creates a Footer in a Google Document. |
-| `create_footnote` | Creates a Footnote segment and inserts a new FootnoteReference at the given location. |
-| `delete_footer` | Deletes a Footer from the document. |
-| `create_header` | Creates a Header in a Google Document. |
-| `delete_header` | Deletes a Header from the document. |
-| `create_paragraph_bullets` | Creates bullets for all of the paragraphs that overlap with the given range. |
-| `delete_paragraph_bullets` | Deletes bullets from all of the paragraphs that overlap with the given range. |
-| `update_paragraph_style` | Updates paragraph styling for a specified range in a Google Document. |
+| `create_document` | Creates a blank Google Document with a specified title using a POST request to the Google Docs API. This is the primary creation method, returning the document's metadata, including the ID required by functions like `get_document` or `insert_text` to perform subsequent operations on the new file. |
+| `get_document` | Retrieves the complete content and metadata for a specific Google Document using its unique ID. This function performs a GET request to the API, returning the full JSON response. It's the primary read operation, contrasting with `create_document` which creates new documents. |
+| `insert_text` | Inserts a text string at a specified index within an existing Google Document using the `batchUpdate` API. This function adds new textual content, distinguishing it from functions that insert non-text elements like tables or apply formatting (`apply_text_style`) to existing content. |
+| `apply_text_style` | Applies character-level formatting such as bold, italic, font size, color, and hyperlinks to a specified text range in a document. This function modifies text appearance, distinguishing it from `update_paragraph_style`, which handles block-level formatting like alignment and headings. |
+| `delete_content_range` | Deletes content within a specified index range in a Google Document via the batchUpdate API. It removes any content based on location, distinguishing it from functions like `delete_header` or `delete_paragraph_bullets`, which remove specific structures or styles instead. |
+| `insert_table` | Inserts a table with specified row and column dimensions at a given index in a Google Document. This function uses the `batchUpdate` API for precise placement, allowing the table to be added to the document's body, a header, or a footer, returning the API's response. |
+| `create_footer` | Creates a footer of a specified type in a Google Document via the batch update API. The footer can optionally be associated with a specific section break, enabling distinct footers for different document sections, distinguishing it from the `create_header` and `create_footnote` functions. |
+| `create_footnote` | Creates a footnote via the batch update API, inserting a numbered reference at a specified index or a segment's end. This function adds an in-body citation, distinguishing it from `create_footer` which creates a content block at the bottom of the page. |
+| `delete_footer` | Deletes a specific footer from a Google Document using its unique ID via a `batchUpdate` request. This operation, the counterpart to `create_footer`, removes an entire footer section, unlike `delete_content_range` which targets text within a specified index range. |
+| `create_header` | Creates a header in a specified Google Document via the batchUpdate API endpoint. This function allows defining the header type and can optionally associate it with a specific section break location. It complements the `delete_header` and `create_footer` functions for managing document structure. |
+| `delete_header` | Removes a specific header from a Google Document using its unique ID. This function sends a `deleteHeader` request to the batch update API, acting as the direct counterpart to `create_header` and distinguishing it from `delete_footer` which removes footers. |
+| `apply_list_style` | Applies a predefined bulleted or numbered list format to paragraphs within a specified range using a `bullet_preset`. This function adds list formatting, distinguishing it from its counterpart, `delete_paragraph_bullets`, and other styling functions like `update_paragraph_style`, which handles alignment and headings. |
+| `delete_paragraph_bullets` | Removes bullet points or numbering from paragraphs within a specified range in a Google Document. This function reverts list formatting via the batch update API, acting as the direct counterpart to `apply_list_style` and preserving the underlying text content, unlike `delete_content_range`. |
+| `update_paragraph_style` | Applies paragraph-level formatting, such as named styles (e.g., 'HEADING_1'), alignment, or text direction, to a specified text range. This function handles block-level styles, distinguishing it from `apply_text_style`, which formats individual characters with attributes like bold or italic. |