Skip to main content
Glama

Read a block's execution logs

get_logs
Read-only

Retrieve recent execution (call) logs for a workspace block, including usage metrics, to see real gateway costs and size batching from production behavior.

Instructions

Returns recent execution (call) logs for a block in a workspace. Each entry carries a usage block (statements, durationMs, fetches, storeOps) for the execution it belongs to — so you can see what a real gateway hit cost, not just your own test runs, and size batching from production behaviour. Entries logged before usage tracking existed simply have no usage.

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": {
      "workspaceId": "<workspaceId>",
      "blockId": "<blockId>"
    },
    "name": "get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
blockIdYes
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already declares this is a safe read. The description does add real return-value context — each entry carries a usage block, and pre-usage-tracking entries lack one — which is useful and not in the annotations. It says nothing about ordering, recency window, or the effect of limit, so it stays at 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the operation and followed by the payoff. Nearly every clause earns its place, though the usage-field enumeration is dense and could be trimmed.

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?

No output schema exists, so describing the returned entry shape falls to the description, and it does cover the usage block and the legacy-entry caveat. It leaves out pagination/limit behaviour and what 'recent' means, which an agent needs to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 3 parameters, so the description carries the full burden. It only implies that blockId/workspaceId identify the target; the limit parameter (1–500), its default, and whether ordering is newest-first are entirely undocumented in both schema and description.

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 opening sentence gives a specific verb and resource: 'Returns recent execution (call) logs for a block in a workspace.' That is enough to distinguish it from sibling tools such as get_block_model or get_workspace_content, but the description never names a sibling or scopes itself explicitly against them.

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?

Usage context is clear and concrete: read production gateway hits rather than only your own test runs, and size batching from real behaviour. There are no exclusions or named alternatives, so it stops short of a full 5.

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