Skip to main content
Glama

get-logs

Retrieve Cloud Logging entries for your current GCP project using filters and pagination to monitor and debug applications.

Instructions

Get Cloud Logging entries for the current project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoFilter for the log entries (see Cloud Logging query syntax)
pageSizeNoMaximum number of entries to return (default: 10)

Implementation Reference

  • Main handler for the 'get-logs' tool. Parses input arguments using Zod schema, checks if a project is selected, initializes the Google Cloud Logging client, retrieves log entries with optional filter and page size, formats the response, and handles errors.
    } else if (name === "get-logs") {
      const { filter, pageSize = 10 } = GetLogsSchema.parse(args);
      
      if (!selectedProject) {
        return createTextResponse("No project selected. Please select a project first.");
      }
    
      try {
        const logging = new Logging({
          projectId: selectedProject
        });
        const [entries] = await logging.getEntries({
          pageSize,
          filter: filter || undefined,
          orderBy: 'timestamp desc'
        });
        
        return createTextResponse(JSON.stringify({
          entries: entries.map((entry: Entry) => ({
            timestamp: entry.metadata.timestamp,
            severity: entry.metadata.severity,
            resource: entry.metadata.resource,
            textPayload: entry.data,
            jsonPayload: typeof entry.data === 'object' ? entry.data : null
          }))
        }, null, 2));
      } catch (error: any) {
        console.error('Error getting logs:', error);
        return createTextResponse(`Error getting logs: ${error.message}`);
      }
  • index.ts:194-211 (registration)
    Registration of the 'get-logs' tool in the listTools response, defining its name, description, and input schema.
    {
      name: "get-logs",
      description: "Get Cloud Logging entries for the current project",
      inputSchema: {
        type: "object",
        properties: {
          filter: {
            type: "string",
            description: "Filter for the log entries (see Cloud Logging query syntax)",
          },
          pageSize: {
            type: "number",
            description: "Maximum number of entries to return (default: 10)",
          }
        },
        required: [],
      },
    }
  • Zod schema used for input validation of the 'get-logs' tool arguments in the handler.
    const GetLogsSchema = z.object({
      filter: z.string().optional(),
      pageSize: z.number().optional(),
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Get Cloud Logging entries' but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires specific permissions, rate limits, pagination details, or what the return format looks like. This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence that front-loads the core purpose without any wasted words. It is appropriately sized for the tool's complexity and gets straight to the point.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like safety, permissions, or return values, which are crucial for a tool that interacts with cloud resources. The high schema coverage helps with parameters but doesn't compensate for other gaps.

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?

The schema description coverage is 100%, so the schema already documents both parameters ('filter' and 'pageSize') with descriptions. The tool description adds no additional meaning beyond what the schema provides, such as examples or constraints, but the high schema coverage justifies the baseline score of 3.

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 verb ('Get') and resource ('Cloud Logging entries for the current project'), making the purpose unambiguous. It doesn't explicitly differentiate from sibling tools like 'list-projects' or 'list-sql-instances', but the resource specificity is sufficient for clarity without being tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as how it differs from other logging or listing tools. It mentions 'current project' but doesn't specify prerequisites or exclusions, leaving usage context implied at best.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RadiumGu/gcp-ops-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server