Skip to main content
Glama

marketplace

by com.gallandigital
OverviewDiscussionsAdmin

get_deployment_guidance

Get deployment guidance for a specific published listing, by listing slug. Read-only, no authentication required (public endpoint, IP rate-limited). Returns title, product_story, included_components, use_cases, complexity_level, product_formats, and demo_video_url when available -- setup and implementation guidance for evaluating or deploying the system after purchase. Call fetch first to confirm the listing exists and get its slug.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe listing's slug, as returned by search or fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"The listing's slug, as returned by search or fetch."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Discloses read-only, no authentication, rate limiting, and returned fields. Lacks error behavior details but covers key aspects without annotations.

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?

Two sentences with no fluff; front-loaded purpose and efficient delivery of all necessary information.

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?

Covers purpose, usage, behavior, and parameters well for a simple tool; could mention output format but not critical without output schema.

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 covers slug with description; description adds context by linking to fetch for slug retrieval, enhancing meaning.

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?

Clearly states the tool retrieves deployment guidance for a published listing by slug, and distinguishes from sibling tools like fetch and search.

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

Usage Guidelines5/5

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

Explicitly advises to call fetch first to obtain the slug, and notes the endpoint is public and IP rate-limited.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources