Skip to main content
Glama
Sign In
Google Cloud MCP Server

Google Cloud MCP Server

by iamishaan24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Query Logs by Time Range

gcp-logging-query-time-range

Query Google Cloud logs within a specified time range using relative times or ISO timestamps, with optional filters and limits.

Instructions

Query Google Cloud Logs within a specific time range. Supports relative times (1h, 2d) and ISO timestamps.

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": {
      "startTime": "<startTime>"
    },
    "name": "gcp-logging-query-time-range"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of log entries to return
filterNoAdditional filter criteria
endTimeNoEnd time in ISO format (defaults to now)
startTimeYesStart time in ISO format or relative time (e.g., "1h", "2d")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior3/5

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

The word 'Query' conveys a read-only operation, and the description adds that relative times and ISO timestamps are supported. However, with no annotations provided, it does not disclose permissions, rate limits, pagination, result format, or any caveats about querying large log ranges, leaving the description to carry a heavier burden than it does.

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 one tightly written sentence that delivers the core purpose and the most important input-format behavior. There is no filler or redundant elaboration.

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 has four documented parameters and no output schema, and the description covers the core behavior but omits return-value expectations and usage differentiators among logging siblings. An agent could invoke it correctly using the schema, but it would lack guidance on whether this tool or a sibling is the right choice for a given request.

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 the baseline is 3. The description mainly repeats the time-format information already present in the startTime parameter description, adding little beyond reinforcing that the tool operates on a time range.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool queries Google Cloud Logs within a specific time range, giving a specific verb and resource. However, it does not explicitly differentiate itself from sibling tools like gcp-logging-query-logs or gcp-logging-search-comprehensive, relying mostly on the tool name for distinction.

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 usage for time-bounded log queries and mentions supported time formats, but it does not provide explicit when-to-use guidance, exclusions, or alternatives. It does not tell an agent when gcp-logging-query-logs or gcp-logging-search-comprehensive would be a better choice.

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