Skip to main content
Glama
Sign In
gemini-researcher

gemini-researcher

by capyBearista
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

fetch_chunk

Retrieve a continuation chunk from a large response. Use when previous response includes chunk metadata to get the next data segment.

Instructions

Retrieve continuation of a large response. Use when a previous tool response included 'chunks' metadata indicating more content available. Example: {cacheKey: 'cache_abc123', chunkIndex: 2}

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": {
      "cacheKey": "<cacheKey>",
      "chunkIndex": "<chunkIndex>"
    },
    "name": "fetch_chunk"
  }
}

Input Schema

NameRequiredDescriptionDefault
cacheKeyYesCache key returned in initial chunked response
chunkIndexYes1-based index of chunk to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It implies a read-only operation ('retrieve') and provides an example, but does not explicitly state that it is non-destructive, any side effects, rate limits, or error conditions. The example helps but leaves gaps.

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?

Two sentences and an example, front-loaded with purpose, followed by usage guidance. Every element is relevant and concise without filler.

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

Completeness3/5

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

For a simple retrieval tool with two params and no output schema, the description explains what it does and when to use it, but does not describe the response format or error handling. It is adequate but not fully complete.

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%, so baseline is 3. The description adds an example showing how cacheKey and chunkIndex relate, but the schema descriptions already cover their meaning. The example adds marginal value beyond the 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 action ('retrieve'), the resource ('continuation of a large response'), and the context (when 'chunks' metadata is present). It distinguishes from siblings like analyze_directory and deep_research by focusing on paginated retrieval.

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?

The description explicitly tells when to use the tool: 'Use when a previous tool response included 'chunks' metadata indicating more content available.' It does not mention when not to use it or alternatives, but the guidance is clear and context-specific.

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