Skip to main content
Glama
sint-marketplace-mcp
by kostyk348

Marketplace Export

marketplace_export

Export the full marketplace registry as an EML bundle with one listing per message, enabling SMTP relay or offline transfer.

Instructions

Export the full registry as EML bundle (one listing per message).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "marketplace_export"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose meaningful behavior beyond the signature: the export covers the ENTIRE registry (no filtering) and the payload is an EML bundle with one listing per message. However, it says nothing about permissions, size/rate limits, or whether the export is a snapshot — all relevant for a bulk read that has no parameters to narrow it.

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?

A single sentence with no filler; the scope ('full registry') is front-loaded and the parenthetical format note is compact and informative.

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?

An output schema exists, so return values need not be re-explained and the description rightly skips them. Its shortfall is routing and behavior: with no annotations and six sibling tools, an agent still cannot tell from this description alone when this export is the right call versus marketplace_pull or marketplace_outbox.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so per the baseline this dimension is not a source of confusion. The description appropriately spends no words on parameters and instead clarifies the fixed scope ('full registry').

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 gives a specific verb ('Export') and resource ('the full registry') plus the output format (EML bundle, one listing per message), so the agent knows exactly what the call produces. It does not distinguish itself from the sibling marketplace_pull, which could plausibly be read as a similar retrieval operation.

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?

There is no guidance on when to choose this over marketplace_pull, marketplace_outbox, or marketplace_search, and no prerequisites or exclusions are stated. The agent is left to infer the scenario from the name alone.

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