Skip to main content
Glama
Sign In
chrome-bridge-mcp

chrome-bridge-mcp

by deng1986
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

read_google_ai_session

Retrieve persisted metadata and visible text from a Google AI conversation session for review or context extraction.

Instructions

Read persisted metadata and current visible text for a Google AI conversation session. Defaults to the active session.

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

Input Schema

NameRequiredDescriptionDefault
sessionIdNoSession id returned by start_google_ai_session. Defaults to the active session.
maxCharsNoMaximum visible conversation text characters to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description must disclose behavior fully. It states it reads data and defaults to active session, but does not mention error handling (e.g., session not found) or any potential side effects. Adequate for a read operation but could be more detailed.

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?

Single sentence with no redundant information. Efficiently conveys the purpose and key behavior.

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?

The tool is simple with two optional parameters, but there is no output schema. The description omits what the returned data looks like (e.g., format of metadata and text). A brief mention of return structure would improve completeness.

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?

Both parameters are fully described in the schema, so the description adds little new information beyond noting the default for sessionId (which is already in the schema). The description does not compensate for schema coverage since coverage is 100%.

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 it reads 'persisted metadata and current visible text' for a Google AI session, and notes it defaults to the active session. This is specific and distinguishes it from sibling tools like start, continue, end.

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?

No explicit when-to-use or when-not-to-use guidance is given. The usage is implied from the description, but alternatives like 'google_ai_read' or 'ask_ai_page' are not mentioned, so the agent lacks comparative context.

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