Skip to main content
Glama

Search gift names

search
Read-onlyIdempotent

Use this when a name may be misspelled, is in Russian or you do not know the kind: fuzzy search over collection, model and backdrop names, returning the best matches with their giftcheckertg.com URLs. Do not use it for prices; open a match with get_collection or get_model. When the user already gave an exact English name, call the get_ tool directly instead.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of matches, default 8.
queryYesText to look for, English or Russian.

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
queryNo
matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds genuinely new context: matching is fuzzy rather than exact, results carry giftcheckertg.com URLs, and prices are out of scope. It stops short of describing result ordering or whether fewer than `limit` matches can be returned.

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?

Three sentences, front-loaded with the trigger condition, then exclusions, then the alternative path. Dense but every sentence carries routing or behavior information; the reference to 'the get_ tool' is slightly loose phrasing but the intent is clear.

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?

For a two-parameter fuzzy search with a defined output schema and full annotation coverage, this is complete: triggers, exclusions, alternatives, and the nature of the returned matches are all stated, and return-value shape is properly delegated to the output schema.

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 both parameters are documented there, including the Russian/English note and the limit default of 8. The description's only added nuance is that queries may be misspelled (fuzzy matching), which is helpful but modest; baseline 3 is appropriate when the schema carries the parameter detail.

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?

States a specific verb and resource — fuzzy search over collection, model and backdrop names — plus the return content (best matches with giftcheckertg.com URLs). It explicitly separates itself from the exact-lookup siblings get_collection/get_model, so an agent can route correctly without opening any schema.

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?

Gives concrete when-to-use triggers (misspelled name, Russian input, unknown kind), an explicit when-not ('Do not use it for prices'), and named alternatives for both cases: get_collection/get_model to open a match and the get_ family for exact English names. Nothing is left to inference.

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