Skip to main content
Glama

Get one TrueGift gift guide with its picks

get_gift_guide
Read-onlyIdempotent

Get one TrueGift gift guide by slug, including its gift picks when available.

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_gift_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe guide slug, e.g. "christmas-gifts-for-her" (from list_gift_guides).

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?

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds one useful behavioral detail beyond that: gift picks are returned only "when available," warning the agent the field may be absent. It says nothing about error behavior for an invalid slug.

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 front-loaded sentence with the resource, the key, and the conditional return behavior. Nothing is padded or repeated.

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 tool with annotations covering safety and no output schema, the description states the input and the shape of the return (guide plus optional picks). Only the not-found/invalid-slug case is left unaddressed.

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% and the single slug parameter is already documented with a concrete example and its source (list_gift_guides). The description restates "by slug" without adding format, validation, or lookup guidance, so it stays at the baseline.

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?

"Get one TrueGift gift guide by slug" names a specific verb (get), a specific resource (a single gift guide), and the lookup key (slug). The word "one" implicitly contrasts with list_gift_guides, but no sibling is named explicitly, so it falls just short of full differentiation.

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?

Usage is implied rather than stated: fetching a single guide requires a slug, and the schema hints the slug comes from list_gift_guides. The description itself gives no explicit when-to-use, when-not-to-use, or alternative (e.g., find_gift_ideas for search-based discovery).

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.