Skip to main content
Glama

marketplace

by com.gallandigital

fetch

Get full detail on one published listing by its listing slug (not a contributor slug). Read-only, no authentication required (public endpoint, IP rate-limited). Returns title, description, short_description, product_story, included_components, use_cases, industry_focus, complexity_level, listing_type, product_formats, thumbnail_url, an array of pricing tiers (name, price_cents, setup_fee_cents, description, billing_interval, features), a contributor object (slug, display_name, badge_tier, bio, credential_summary, credential_badges), and a category object (name, slug). Use after search or list_categories to drill into a specific result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe listing's slug, as returned by search (the listing-level slug, not a contributor slug).

TDQS

A4.6/5.0
Behavior5/5

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

Discloses behavior: 'Read-only, no authentication required (public endpoint, IP rate-limited)'. Describes return structure in detail. No annotations present, so description fully covers transparency.

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?

Front-loaded with purpose and usage, then return fields. Slightly long due to detailed return description, but every sentence adds value. No redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description is highly complete: explains purpose, when to use, parameter, and return structure. No gaps for the tool's complexity.

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?

Schema coverage is 100% with description of slug. Description adds value by clarifying 'listing-level slug, not a contributor slug', which prevents confusion. Baseline 3 plus extra clarification.

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

Purpose5/5

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

The description specifies the verb 'Get', resource 'full detail on one published listing', and identifier 'listing slug'. It clearly distinguishes from siblings like search and list_categories by stating the scope.

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

Usage Guidelines4/5

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

Explicitly states when to use: 'Use after search or list_categories to drill into a specific result.' Also notes read-only and no authentication. Lacks explicit when-not but covers key usage context.

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

All marketplace toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: search for discovery, list_categories for browsing, fetch for listing details, get_contributor_profile for contributor info, and get_deployment_guidance for deployment guidance. There is no overlap in functionality.

Naming Consistency3/5

Tool naming is inconsistent: 'fetch' and 'search' are bare verbs, while others follow a verb_noun pattern (get_contributor_profile, get_deployment_guidance, list_categories). A uniform pattern like 'get_listing'/'search_listings' would improve predictability.

Tool Count5/5

With 5 tools covering search, categories, listing details, contributor profiles, and deployment guidance, the set is well-scoped for browsing a marketplace. Each tool serves a necessary role without redundancy.

Completeness4/5

The tool surface covers key browsing operations: discovery (search, categories), detail (fetch), contributor info, and deployment guidance. Minor gaps exist, such as the lack of a tool for listing reviews or filtering search by category directly, but the core workflow is supported.

Resources