Skip to main content
Glama

Get marketplace details

get_marketplace
Read-only

Details for one marketplace by slug (from list_marketplaces), incl. public API endpoint and caveats.

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": {
      "slug": "<slug>"
    },
    "name": "get_marketplace"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes that this is a non-mutating lookup, so the description carries a lighter burden. It adds useful behavioral context by noting the response includes the public API endpoint and caveats, but says nothing about failure behavior for an invalid slug or whether the result can be empty.

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 that front-loads the resource, then the lookup key, then the payload highlights. No filler or repetition of the title.

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 one-parameter read-only lookup with an annotation covering safety, the description covers the identifier source and the notable return contents, which is enough to call it correctly. The remaining gap is error/empty-result behavior, which is minor for this tool shape.

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 coverage is 0% and the schema only types slug as a string, so the description must supply meaning. It does add real information by identifying the slug as a marketplace identifier sourced from list_marketplaces, but it gives no format, casing, or validity rules for the value.

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?

States a specific verb-and-resource pair ('Details for one marketplace') and scopes it to a single entity by slug, which separates it from the list-level sibling list_marketplaces. It also previews the payload ('public API endpoint and caveats'), so the agent knows what it gets back.

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

Usage Guidelines3/5

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

The parenthetical '(from list_marketplaces)' implicitly tells the agent to obtain the slug via the listing tool first, which is genuine usage context. However, there is no explicit when-not-to-use guidance, no statement that this is the only way to read a single marketplace, and no handling advice for an unknown slug.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources