Skip to main content
Glama
IgorGanapolsky

ThumbGate

by IgorGanapolsky
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

search_thumbgate

Read-only

Retrieve ThumbGate state by searching across feedback logs, ContextFS memory, prevention rules, and policy documents.

Instructions

Search raw ThumbGate state across feedback logs, ContextFS memory, prevention rules, and imported policy documents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for ThumbGate state.
limitNoMaximum results to return (default 10)
sourceNoRestrict search to a single ThumbGate source.
signalNoOptional feedback-signal filter when searching feedback data.

Implementation Reference

  • adapters/mcp/server-stdio.js:105-115 (registration)
    Import/registration of searchThumbgate into the MCP adapter (server-stdio.js). The function is imported from '../../scripts/thumbgate-search' on line 106.
    const {
  searchThumbgate,
} = require('../../scripts/thumbgate-search');
const {
  buildMultimodalRetrievalPlan,
} = require('../../scripts/multimodal-retrieval-plan');
const {
  importDocument,
  listImportedDocuments,
  readImportedDocument,
} = require('../../scripts/document-intake');
  • adapters/mcp/server-stdio.js:600-607 (handler)
    MCP case handler for 'search_thumbgate': enforces rate limit, then calls searchThumbgate with args (query, limit, source, signal) and wraps the result via toTextResult.
    case 'search_thumbgate':
  enforceLimit('search_thumbgate');
  return toTextResult(searchThumbgate({
    query: args.query,
    limit: args.limit,
    source: args.source,
    signal: args.signal,
  }));

Tool Definition Quality

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint: true, so the read-only nature is clear. The description does not contradict annotations. However, it adds no additional behavioral context (e.g., pagination, rate limits, or the meaning of 'raw' state). For a tool with full annotation coverage, the description adequately reinforces behavior without adding extra detail.

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?

The description is a single, front-loaded sentence that immediately states the action (Search) and the resource (raw ThumbGate state) followed by the scope (across four sources). No filler or redundant information; every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the tool searching multiple structured sources and having no output schema, the description omits key context: the structure or format of results, whether results are combined or per-source, and any limitations (e.g., pagination default). An agent would lack sufficient understanding of the output to use the tool effectively without additional inference.

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?

Input schema has 100% description coverage, with all four parameters already well-defined. The description adds no further parameter-specific meaning beyond restating the sources (which matches the 'source' enum). Since schema carries the full burden, the description's marginal contribution earns the baseline score of 3.

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 tool searches raw ThumbGate state across four specific sources (feedback logs, ContextFS memory, prevention rules, imported policy documents). This distinguishes it from sibling search tools like search_lessons or session_search by specifying the domain (ThumbGate) and the exact data sources.

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?

The description implies when to use the tool—when needing ThumbGate state across multiple sources—but does not provide explicit guidance on when not to use it or how it compares to siblings like search_lessons. Given the many sibling search tools, explicit exclusions or alternative recommendations would improve clarity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IgorGanapolsky/ThumbGate'

If you have feedback or need assistance with the MCP directory API, please join our Discord server