Skip to main content
Glama
Sign In
ThumbGate

ThumbGate

by IgorGanapolsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Plan Multimodal Retrieval

plan_multimodal_retrieval
Read-only

Plan multimodal retrieval rollouts for screenshots, PDFs, dashboards, and proof artifacts without GPU training.

Instructions

Plan a high-ROI multimodal retrieval rollout for screenshots, PDF pages, dashboard captures, and proof artifacts without starting GPU training.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_multimodal_retrieval"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoBusiness or workflow objective for visual/document retrieval.
corpusItemsNoEstimated number of visual artifacts or document pages to index.
useRerankerNoWhether to include a multimodal reranker stage after initial embedding retrieval.
evidenceTypesNoEvidence surfaces to include, such as screenshots, pdf_pages, proof_artifacts, dashboards, or videos.
latencyBudgetMsNoTarget retrieval latency budget for agent recall.
maxEmbeddingDimNoMaximum embedding dimension to budget for Matryoshka-style truncation planning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.23.1
  2. Removedv1.21.2
  3. Addedv1.16.9

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true; the description adds that the tool plans but does not execute or require GPU training. However, it does not disclose other behavioral aspects like idempotency or side effects. With annotations covering safety, the description adds moderate value.

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?

The description is a single sentence that efficiently conveys the tool's purpose and scope. It is front-loaded with the key action ('Plan') and resource. Could be slightly more structured but is not verbose.

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?

With 6 parameters and no output schema, the description should explain what the output or result looks like (e.g., a retrieval plan or recommendation). It lacks this information, leaving the agent uncertain about what to expect when invoking the tool.

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 100%, so parameters are already well-documented. The description only lists example evidence types (screenshots, PDF pages), which partially overlaps with the 'evidenceTypes' parameter. No additional semantic information beyond schema.

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's purpose: 'Plan a high-ROI multimodal retrieval rollout.' It specifies the resource (multimodal retrieval for screenshots, PDF pages, etc.) and distinguishes from siblings by being a planning tool (not execution or retrieval). The phrase 'without starting GPU training' adds specificity.

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 (planning a retrieval rollout without GPU training) but does not explicitly state when not to use it or suggest alternatives. No comparison to sibling tools is provided. The guidance is adequate but minimal.

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

Deploy Server

Other Tools