Skip to main content
Glama
Arnie936

MCP All-in-One Server

by Arnie936

send_to_webhook

Transmits a text prompt to an n8n webhook and returns the processed response.

Instructions

Send a prompt to the n8n webhook and get the response.

Args: prompt: The text prompt to process

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'send_to_webhook' tool. It sends a prompt to an n8n webhook via HTTP POST and returns the response text. Registered with @mcp.tool() decorator.
    @mcp.tool()
    async def send_to_webhook(prompt: str) -> str:
        """Send a prompt to the n8n webhook and get the response.
    
        Args:
            prompt: The text prompt to process
        """
        webhook_url = "Your_URL"
        
        async with httpx.AsyncClient() as client:
            try:
                response = await client.post(webhook_url, json={"prompt": prompt}, timeout=30.0)
                response.raise_for_status()
                return response.text
            except httpx.HTTPError as e:
                return f"Error sending request: {str(e)}"
  • Registration of the 'send_to_webhook' tool using the @mcp.tool() decorator on the FastMCP server instance.
    @mcp.tool()
Behavior2/5

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

With no annotations, the description should disclose side effects, auth needs, or error behavior, but only says 'send and get response', lacking transparency.

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 very short and to the point, but could include more detail without being verbose.

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

Completeness3/5

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

For a simple tool, the description covers the basic purpose but lacks details about the webhook, response format, or error handling, leaving gaps.

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

Parameters3/5

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

The description adds meaning to the 'prompt' parameter (text prompt to process) beyond the schema's type-only definition, but coverage is minimal.

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 sends a prompt to an n8n webhook and returns a response, distinguishing it from the arithmetic sibling tools.

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?

No guidance on when to use this tool, no mention of alternatives or when not to use it.

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/Arnie936/Agentic-MCP'

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