Skip to main content
Glama

marketplace

by com.gallandigital

search

Full-text search across GallanDigital's published, buyer-facing listings only. Read-only, no authentication required (public endpoint, IP rate-limited). Returns an array of listing summaries, each with title, slug, short_description, price_cents, currency, listing_type, complexity_level, category_slug, and a nested contributor object (slug, display_name). Use as the entry point for discovery -- pass a result's slug to fetch for full listing detail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
queryYesSearch terms to match against listing title, description, and tags.
industryNoOptional: restrict results to listings tagged for a specific industry vertical (matches industry_focus).
category_slugNoOptional: restrict results to one category slug. Call list_categories first for valid values.

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description fully discloses read-only nature, authentication requirements (none), rate limiting, and return structure with exact field names. No contradictions.

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?

Very concise yet complete: three sentences covering purpose, safety/access, return format, and usage workflow. Front-loaded with the most critical information.

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?

Covers all essential aspects: search scope, constraints, return structure, and integration with siblings. Despite no output schema, the field enumeration compensates fully.

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 100% with well-described parameters. The description adds no additional parameter meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 clearly states the verb 'Full-text search' and the specific resource 'published, buyer-facing listings only', and distinguishes itself from sibling tool 'fetch' by positioning itself as the entry point for discovery.

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?

Provides clear context: read-only, no authentication, public endpoint with rate limits, and explicitly instructs to use 'fetch' for full detail. Lacks explicit when-not-to-use scenarios but gives strong directional guidance.

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