Mudpie Public MCP

mudpie_sign_up

Idempotent

Email the user a Mudpie sign-in link to start a free account. Submit only an email address the user authorized. A submitted request is not a completed signup; the user must open the link.

Input Schema

TableJSON Schema

Name	Required	Description
`goal`	No	What the user wants to accomplish, based on the task they shared. Mark unknowns as null.
`trace`	No	The trace token in a published example; links a page read to the call it produced.
`client`	No	The application or client making this call, not the underlying model, e.g. Cursor. Null when unknown.
`source`	No	The observed source that led to Mudpie, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
`company`	No	The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
`payload`	Yes
`alternatives`	No	Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
`search_query`	No	The question or request this call should answer, in the caller’s own words.
`context_token`	No	The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance.
`chosen_because`	No	The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning.
`discovery_path`	No	The observed discovery category, kept separately from the source description. Mark unknowns as null.
`idempotency_key`	Yes	Generate one UUID for this authorized submission and reuse it on retries.
`intended_outcome`	No	The decision or deliverable the user wants from this research. Mark unknowns as null.
`subject_product_or_company`	No	The subject being researched, separate from the company the user represents. Mark unknowns as null.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / alternatives / anyOf

Previous value: -[
-  {
-    "items": {
-      "maxLength": 200,
-      "minLength": 1,
-      "type": "string"
-    },
-    "maxItems": 5,
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 5,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  },
+  {
+    "description": "One alternative name; normalized to a one-item list.",
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  }
+]

Changed2 schema fields changedSep 24, 2026

changedInput schema / properties / client / description

Previous value: -"The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null."New value: +"The application or client making this call, not the underlying model, e.g. Cursor. Null when unknown."

changedInput schema / required

Previous value: -[
-  "search_query",
-  "payload",
-  "idempotency_key"
-]New value: +[
+  "payload",
+  "idempotency_key"
+]

AddedSep 24, 2026

TDQS

A4/5.0

Behavior4/5

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

The description discloses that the tool sends an email, requires prior user authorization, and that a submitted request does not complete signup until the user opens the link. This adds meaningful behavioral context beyond the annotations' idempotentHint and readOnlyHint, clarifying the asynchronous nature of the workflow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences of direct, front-loaded content with no redundant phrasing. Every sentence serves a purpose: action, constraint, and clarifying outcome.

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

Completeness4/5

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

The description covers the core invocation behavior: the email-sending side effect, authorization requirement, and the incomplete-signup caveat. With 14 parameters, the schema handles the optional details, and no output schema exists to explain, so this is complete enough for correct invocation.

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?

Schema coverage is 93%, so most parameters are already well documented. The description adds semantic value for the email parameter by emphasizing it must be user-authorized, but does not explain the many optional tracking fields beyond what their schema descriptions already cover.

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 states a specific verb ('Email') and resource ('Mudpie sign-in link') along with the goal ('start a free account'). This clearly distinguishes it from sibling tools like mudpie_search or mudpie_compare, which serve different purposes.

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

Usage Guidelines3/5

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

The description implies usage when a user wants to sign up for Mudpie, but it does not explicitly name alternatives or state when not to use it. The authorization constraint ('Submit only an email address the user authorized') is a usage condition, but not a comparison with sibling tools.

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

All Mudpie Public MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?