Skip to main content
Glama

read_gemini_log

Read-only

Retrieve entries from the shared Gemini log to recall earlier Gemini answers. Filter by id, tool, or search text and return the last N matches.

Instructions

Return entries of the shared Gemini log (docs/ai/GEMINI_LOG.md), to recall earlier Gemini answers. Filter by id, tool or a search text; returns the last N matches.

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": "read_gemini_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoReturn only this entry.
toolNoOnly entries of this tool, e.g. "gemini_review".
queryNoOnly entries containing this text (case-insensitive).
last_nNoNumber of entries (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint already establishes the safety profile, so the description's job is to add retrieval semantics — which it does by disclosing that results are the 'last N matches' (i.e., recency ordering with truncation). It doesn't cover edge cases like an empty or missing log file, but the added value over the annotation is real.

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 tight sentences: the first identifies the resource and purpose, the second covers filtering and result limits. Nothing is redundant or buried, and the most important information leads.

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?

For a read-only lookup tool with full schema descriptions and readOnlyHint, the definition is nearly complete — resource, purpose, filters, and result count are all covered. The only omission is any indication of what an entry contains, which matters slightly given there is no 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% with per-parameter descriptions and even a regex pattern for id, so the schema already carries the semantics. The description only restates the three filters and the 'last N' concept without adding syntax or matching behavior beyond what the schema states.

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 pairs a specific verb ('Return entries') with a specific resource (the shared Gemini log at docs/ai/GEMINI_LOG.md) and states the intent ('to recall earlier Gemini answers'). That concrete file location plus the read-focused purpose makes it clearly distinct from siblings like ask_gemini or gemini_review.

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 phrase 'to recall earlier Gemini answers' implies the use case (looking up prior output rather than generating new output), and the filter options sketch typical usage. However, it never states when not to use it or explicitly routes to alternatives such as ask_gemini for a fresh answer, leaving the agent to infer the boundary.

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