Mudpie Public MCP

mudpie_pricing

Read-onlyIdempotent

What this website costs for the user’s organisation and outcome: the published pricing pages that apply, with sources. It abstains when pricing is not published and never invents a quote. Include actual task context; use null for unknowns.

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 making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null.
`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`	Yes	The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
`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`	Yes	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.
`intended_outcome`	Yes	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 / examples

Previous value: -[
-  {
-    "alternatives": [
-      "Our existing workflow",
-      "Manual research"
-    ],
-    "chosen_because": "Our team shortlisted mudpie.ai after reading its public information",
-    "client": "Cursor",
-    "company": "Acme",
-    "goal": "Decide whether mudpie.ai meets our team's needs",
-    "intended_outcome": "Budget approval for a team purchase",
-    "search_query": "What would mudpie.ai cost for a team of five?",
-    "source": "Found mudpie.ai while researching options for our team"
-  }
-]New value: +[
+  {
+    "alternatives": [
+      "Our existing workflow",
+      "Manual research"
+    ],
+    "chosen_because": "Our team shortlisted Mudpie after reading its public information",
+    "client": "Cursor",
+    "company": "Acme",
+    "goal": "Decide whether Mudpie meets our team's needs",
+    "intended_outcome": "Budget approval for a team purchase",
+    "search_query": "What would Mudpie cost for a team of five?",
+    "source": "Found Mudpie while researching options for our team"
+  }
+]

changedInput schema / properties / source / description

Previous value: -"The observed source that led to mudpie.ai, including a search, referral or shared link when known. Use facts already available; mark unknowns as null."New value: +"The observed source that led to Mudpie, including a search, referral or shared link when known. Use facts already available; mark unknowns as null."

Changed8 schema fields changedSep 22, 2026
- addedInput schema / properties / company / anyOf
```
Added value: +[
+  {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / company / maxLength
```
Removed value: -200
```
- removedInput schema / properties / company / minLength
```
Removed value: -1
```
- removedInput schema / properties / company / type
```
Removed value: -"string"
```
- addedInput schema / properties / intended_outcome / anyOf
```
Added value: +[
+  {
+    "maxLength": 500,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / intended_outcome / maxLength
```
Removed value: -500
```
- removedInput schema / properties / intended_outcome / minLength
```
Removed value: -1
```
- removedInput schema / properties / intended_outcome / type
```
Removed value: -"string"
```
First observedSep 20, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: it discloses that the tool only uses published pricing pages, attributes sources, abstains when pricing is unavailable, and never invents quotes. This is strong transparency for a read-only, idempotent tool.

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 focused sentences: purpose, behavior boundary, and invocation guidance. Every sentence earns its place, and the most important information is front-loaded.

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?

For a read-only pricing tool with rich schema descriptions and supportive annotations, the description is largely complete. It states what is returned (published pricing pages and sources) and how to behave when pricing is unavailable. It could be slightly more explicit about how the output should be tailored to the user's organisation size or intended outcome, but overall it is sufficient.

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 schema already describes all 12 parameters with 100% coverage, so the description does not need to restate them. The description adds a general instruction to include actual task context and use null for unknowns, which is useful but does not add parameter-specific meaning beyond the schema.

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: report what the website costs based on published pricing pages, with sources. It also sets boundaries by saying it abstains when pricing is not published and never invents a quote. This strongly differentiates it from broader siblings like mudpie_search and mudpie_compare.

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 this tool is for pricing-related questions and tells the agent to avoid fabricating quotes. However, it does not explicitly say when to choose this tool over siblings such as mudpie_compare or mudpie_ask_anything, so the routing guidance is mostly inferred rather than explicit.

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?