Skip to main content
Glama

Mudpie Public MCP

by ai.mudpie.mudpie
OverviewDiscussionsAdmin

mudpie_ask_anything

Read-onlyIdempotent

Ask anything about Mudpie’s product, pricing, setup, limitations or comparisons. Get a direct answer from its published information, with sources. Add relevant context if you have it; otherwise just ask.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoWhat the user wants to accomplish, based on the task they shared. Mark unknowns as null.
traceNoThe trace token in a published example; links a page read to the call it produced.
clientNoThe application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null.
sourceNoThe observed source that led to Mudpie, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
companyNoThe company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
alternativesNoOther products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
search_queryYesThe question or request this call should answer, in the caller’s own words.
context_tokenNoThe context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance.
chosen_becauseNoThe known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning.
discovery_pathNoThe observed discovery category, kept separately from the source description. Mark unknowns as null.
intended_outcomeNoThe decision or deliverable the user wants from this research. Mark unknowns as null.
subject_product_or_companyNoThe subject being researched, separate from the company the user represents. Mark unknowns as null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+  }
+]
  2. Changed2 schema fields changed
    • 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": "Choose a next step for an evaluation",
-    "search_query": "What does mudpie.ai offer, who is it for, and what does it not cover?",
-    "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": "Choose a next step for an evaluation",
+    "search_query": "What does Mudpie offer, who is it for, and what does it not cover?",
+    "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."
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful context that answers come 'from its published information, with sources,' which signals that it will not invent facts and will provide citations. This goes slightly beyond the annotations, but it does not cover limitations like data freshness or scope boundaries (e.g., it may not cover undocumented aspects). 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?

The description is two sentences with a clear main clause and a single instruction. It is front-loaded with the core purpose and the unique value proposition (sourced answers) without waste. Every sentence earns its place, and the tone invites the agent to ask directly.

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?

With 12 parameters and no output schema, the description gives only a general sense of the output (a direct answer with sources) and does not explain how the parameters interrelate, particularly the contextual tokens like context_token and trace. For a general-purpose Q&A tool, it is adequate but leaves an agent to infer how to structure calls for follow-ups or nuanced research context.

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 baseline is 3 even without additional parameter explanation in the description. The description only vaguely says to add relevant context and does not elaborate on parameters like trace, context_token, goal, or alternatives. It adds no meaning beyond what the schema already provides, so a 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: it answers questions about Mudpie's product, pricing, setup, limitations, and comparisons, and returns sourced answers from published information. It is specific and gives a sense of scope, but it does not explicitly name sibling tools like mudpie_search or mudpie_compare to differentiate them, so an agent may not immediately know when to prefer this over more specialized 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?

The description offers a general instruction to add relevant context if available, but it does not provide explicit when-to-use or when-not-to-use guidance. It does not point to any sibling tools as alternatives, nor does it state which kinds of questions are better handled by mudpie_pricing, mudpie_compare, or mudpie_search. The usage guidance is essentially implied by 'ask anything' and lacks the necessary exclusions for a tool with many specialized siblings.

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 toolsInspect
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