Skip to main content
Glama

Search GTM Vault

search_vault
Read-only

Search every GTM Vault Podcast, Show Me Your Stack and Coffee Walk episode, write-ups and transcripts. Use when the user asks how operators handled a GTM problem, what a guest said about a topic, or wants evidence for a recommendation. Returns short excerpts with episode links and, for transcript matches, a timestamp link. Each result carries its episode code.

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

Input Schema

NameRequiredDescriptionDefault
showNoall
limitNo
queryYes
content_typeNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover read-only/open-world; the description adds genuinely new behavior — short excerpts, episode links, timestamp deep links for transcript hits, and an episode code per result. It does not say how results are ranked or what happens when nothing matches.

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?

Four tight sentences, front-loaded with scope, then usage, then return shape. No filler or restatement of the tool title.

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?

With no output schema, the description correctly spends its space on return shape (excerpts, links, timestamps, episode codes), and annotations cover safety. Only ranking behavior and empty-result handling are left unstated.

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 description coverage is 0%, so the description must carry parameter meaning; it only implicitly maps 'episodes' to `show` and 'transcript matches' to `content_type`, and never explains the 'smys'/'coffee_walk' abbreviations, the default limit of 5, or the max of 10.

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 ('Search') over a specific, enumerated resource set ('GTM Vault Podcast, Show Me Your Stack and Coffee Walk episode, write-ups and transcripts'), which distinguishes it from the get_/list_ siblings that retrieve a single named object.

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?

Explicit use triggers are given: user asks how operators handled a GTM problem, what a guest said, or wants evidence for a recommendation. No when-not-to-use or named alternative is offered, which keeps it below a 5.

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