FOAAS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| foaas_thanksA | Use for sarcastic thanks, ironic gratitude, expressing annoyance while thanking, or responding to unwanted help. |
| foaas_awesomeA | Use for enthusiastic celebration, expressing excitement, praising success, or showing genuine enthusiasm about something great. |
| foaas_legendA | Use for praising someone highly, calling someone amazing, recognizing exceptional work, or complimenting heroic efforts. Requires a target person. |
| foaas_daltonA | Use when praising someone for solving difficult problems, fixing critical issues, being a hero, or handling tough situations brilliantly. Requires a target person. |
| foaas_becauseA | Use when answering "why" questions dismissively, refusing to explain, rejecting requests emphatically, or shutting down interrogations. |
| foaas_zeroA | Use when expressing complete disinterest, showing zero concern, indicating you don't care at all, or dismissing something as unimportant. |
| foaas_byeB | Use for ending conversations emphatically, saying goodbye dismissively, terminating discussions, or leaving a situation dramatically. |
| foaas_offB | Use for direct dismissal of someone, telling a person to go away, rejecting someone firmly, or expressing strong disapproval of an individual. Requires a target. |
| foaas_gfyA | Use for military-style dismissal, telling someone off in a formal manner, dismissing with phonetic code, or adding professional flair to profanity. Requires a target. |
| foaas_chainsawB | Use for expressing sarcastic disbelief, showing exaggerated shock at someone, reacting to absurdity, or using pop culture references. Requires a target. |
| foaas_keepB | Use for dealing with persistent annoyances, dismissing someone who keeps bothering you, extended rejection, or emphasizing that someone should stay away. Requires a target. |
| foaas_everyoneA | Use for dismissing everyone at once, expressing frustration with all parties, universal rejection, or showing you're done with everything and everyone. |
| foaas_flyingB | Use for expressing maximum indifference, showing extreme lack of concern, emphasizing you really don't care, or dismissing something as completely irrelevant. |
| foaas_assholeA | Use for general insults, self-deprecation, expressing anger broadly, or making a non-specific negative statement. No target needed. |
| foaas_logsD | Use when someone asks about runtime errors, debugging issues, "it doesn't work" problems, or when the solution is clearly in the logs. Perfect for lazy debugging requests. |
| foaas_rtfmA | Use for questions clearly answered in documentation, basic issues that show no research effort, lazy requests, or RTFM situations. Perfect response to "how do I do X?" when X is in the docs. |
| foaas_thinkB | Use for questionable code, bad decisions in PRs, WTF commits, poor architectural choices, or when reviewing something that makes you wonder about the author's thought process. |
| foaas_thinkingA | Alternative phrasing for questioning someone's thought process. Use for similar scenarios as foaas_think - bad code, poor decisions, questionable commits. Offers variety in tone. |
| foaas_shutupA | Use for bikeshedding, endless debates, off-topic discussions, nitpicking in code reviews, or when someone won't stop arguing about trivial matters. Direct and unambiguous dismissal. |
| foaas_lookB | Use when requesting code review, pointing out issues in someone's work, drawing attention to problems, or asking someone to examine something specific. More direct than a polite review request. |
| foaas_ridiculousA | Use for absurd requirements, impossible deadlines, unrealistic feature requests, or situations that are clearly beyond reasonable. Perfect for scope creep and feature bloat discussions. |
| foaas_understandA | Use when requirements are unclear, code is confusing, documentation is missing, or someone's explanation makes no sense. Expresses genuine confusion about what someone is trying to communicate. |
| foaas_coolB | Use for sarcastic approval, dismissing excuses, responding to lengthy explanations that don't matter, or when someone is making excuses for failures. Peak sarcasm energy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/gusztavvargadr/foaas-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server