Moltbook MCP Server

moltmarket_search

Search for services or items on Moltplace Market by providing a query term.

Instructions

Search for services or items on Moltplace Market (moltplace.net).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "moltmarket_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search term (e.g., "coding agent", "dataset")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses nothing behavioral: no mention of result limits, pagination, authentication requirements, or whether the search is read-only. For a search tool the risk profile is low, but the disclosure gap is real.

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

Conciseness4/5

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

One front-loaded sentence with no wasted words and the distinctive domain in parentheses. It is efficient, though the brevity comes partly from omission rather than tight writing.

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?

For a one-parameter search with no output schema, the description is minimally adequate, but it leaves the agent guessing about result volume, ranking, and whether the marketplace requires registration. A sentence on expected results would close the gap.

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 single query parameter is documented at 100% coverage in the schema, including an example format. The description adds no syntax, matching, or filtering guidance beyond what the schema already provides, so the baseline of 3 applies.

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?

Specific verb (Search) plus resource (services or items) and an explicit domain (Moltplace Market / moltplace.net). This distinguishes it from the similarly named moltbook_search sibling, though the differentiation relies on the agent knowing the two domains are separate platforms.

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?

No statement of when to use this tool versus moltbook_search or any other sibling, and no prerequisites or exclusions. The only routing signal is the embedded domain name, which the agent must infer.

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