Mudpie Public MCP

mudpie_compare

Read-onlyIdempotent

Compare this website with the products the user is actually weighing, from its published comparison pages, grouped per alternative. Alternatives it has no page for are named as not covered. 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`	No	The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
`alternatives`	Yes	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`	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.

Changed5 schema fields changedSep 26, 2026

addedInput schema / properties / alternatives / anyOf

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

removedInput schema / properties / alternatives / items

Removed value: -{
-  "maxLength": 200,
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / alternatives / maxItems
```
Removed value: -5
```
removedInput schema / properties / alternatives / minItems
```
Removed value: -1
```
removedInput schema / properties / alternatives / type
```
Removed value: -"array"
```

Changed2 schema fields changedSep 24, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "alternatives": [
-      "Our current tool"
-    ],
-    "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": "Choose a next step for an evaluation",
-    "search_query": "How does mudpie.ai compare for our team's use case?",
-    "source": "Found mudpie.ai while researching options for our team"
-  }
-]New value: +[
+  {
+    "alternatives": [
+      "Our current tool"
+    ],
+    "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": "Choose a next step for an evaluation",
+    "search_query": "How does Mudpie compare for our team's use case?",
+    "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."

First observedSep 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds meaningful behavioral details beyond the readOnly, idempotent, openWorld annotations: it reads published comparison pages, groups results per alternative, and names uncovered alternatives. It also instructs to include actual task context and use null for unknowns, which shapes caller behavior. No contradiction with annotations.

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?

Two sentences with no filler. The primary action is front-loaded ('Compare this website with the products the user is actually weighing'), followed by specific behavioral details. Every clause earns its place.

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 tool with 12 parameters and no output schema, the description is sufficient because the schema fully documents parameters and annotations cover safety. It explains the core behavior and handling of unknowns. It does not describe the output format, but that is not required given the tool's purpose and available structured data. Minor gap: it does not mention the context_token or trace, but these are optional and documented in the schema.

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 description coverage is 100%, so the schema already documents all 12 parameters thoroughly. The description does not add parameter-specific meaning beyond reinforcing the 'use null for unknowns' pattern already present in the schema. Baseline 3 is appropriate since the schema carries the full burden.

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 compares this website against the user's actual alternatives using published comparison pages, grouping per alternative and naming uncovered ones. It uses a specific verb ('compare'), a clear resource (this website), and distinct behavior that separates it from sibling tools like mudpie_search or mudpie_page_tldr.

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

Usage Guidelines4/5

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

The description gives clear context on when to use it: when the user is weighing alternatives and needs a comparison. It implies the intended use case without explicitly listing exclusions or alternatives, but the context is strong enough to guide selection. It does not name sibling tools or when not to use, but the purpose is unambiguous.

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?