MCP's default query parameter hallucination

deviantintegral · December 1, 2025, 7:54pm

While the MCP doesn’t have a stable release tagged, I’m suspicious it hasn’t been tested much by humans at all. In going through the default setup, I noticed that it recommends a default query parameter of order:latest-post which looks to be hallucinated. The MCP has clearly been written with significant AI tooling. Perhaps the README needs to be updated to be clear on what has been tested and what is still in progress?

Falco · December 1, 2025, 8:33pm

latest-post is a valid parameter in the filter route:

github.com/discourse/discourse

lib/topics_filter.rb

main


      
          { name: "status:unlisted", description: I18n.t("filter.description.status_unlisted") },
          { name: "status:deleted", description: I18n.t("filter.description.status_deleted") },
          { name: "status:public", description: I18n.t("filter.description.status_public") },
          { name: "order:", description: I18n.t("filter.description.order"), priority: 1 },
          { name: "order:activity", description: I18n.t("filter.description.order_activity") },
          { name: "order:activity-asc", description: I18n.t("filter.description.order_activity_asc") },
          { name: "order:category", description: I18n.t("filter.description.order_category") },
          { name: "order:category-asc", description: I18n.t("filter.description.order_category_asc") },
          { name: "order:created", description: I18n.t("filter.description.order_created") },
          { name: "order:created-asc", description: I18n.t("filter.description.order_created_asc") },
          { name: "order:latest-post", description: I18n.t("filter.description.order_latest_post") },
          {
            name: "order:latest-post-asc",
            description: I18n.t("filter.description.order_latest_post_asc"),
          },
          { name: "order:likes", description: I18n.t("filter.description.order_likes") },
          { name: "order:likes-asc", description: I18n.t("filter.description.order_likes_asc") },
          { name: "order:likes-op", description: I18n.t("filter.description.order_likes_op") },
          { name: "order:likes-op-asc", description: I18n.t("filter.description.order_likes_op_asc") },
          { name: "order:posters", description: I18n.t("filter.description.order_posters") },
          { name: "order:posters-asc", description: I18n.t("filter.description.order_posters_asc") },

What do you mean?

sam · December 1, 2025, 11:43pm

I think it may be a legit bug in the README… feel free to post a PR if you notice any other inaccuracies, thanks for bringing this up:

Topic		Replies	Views
Add site setting to default search results sort by latest post instead of relevance Feature search , completed	24	2667	November 28, 2023
Experimental topics list filter feature Feature feedback , experimental , topic-filter	42	3974	November 24, 2024
Sort latest by no replies + most recent Support	3	447	May 16, 2023
Viewing open / archived or closed topics Feature	28	6665	January 3, 2015
Add "orderdesc" modification to advanced search Feature	6	1537	November 4, 2022

MCP's default query parameter hallucination

Related topics