Skip to main content
Glama

Show the AI log

ai_log
Read-only

Show what an AI app read from local files and databases, including when, route, allowed profiles/versions, tables/columns, and row counts—without exposing values.

Instructions

Show the AI log's summary (for 'what did my AI see?'): every read, with when, which AI app, the route, the profiles and versions that allowed it, the tables and columns at the level each was shown, and how many rows. Never the values. Optional start and end are dates (YYYY-MM-DD, both included).

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

Input Schema

NameRequiredDescriptionDefault
endNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds a genuinely useful behavioral fact: results are a summary that never exposes underlying values, plus inclusive date-bound semantics. It omits ordering, result caps, and what happens with no date range, which keeps it short of a 5.

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 sentences, front-loaded with the resource and purpose, then the returned fields, then the parameters. Every clause carries distinct information and there is no filler or restatement of the title.

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?

With no output schema, the field enumeration in the description effectively substitutes for one, and the parameter semantics are fully spelled out for a simple two-param read tool. Minor omissions such as ordering, limits, or empty-result behavior keep it from being fully complete.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the load, and it does: both parameters are identified as optional dates, with an explicit YYYY-MM-DD format and the note that both bounds are included. It does not say what the default range is when they are omitted, leaving one gap.

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?

States a specific verb and resource ("Show the AI log's summary") and enumerates exactly what the summary contains: when, which AI app, route, profiles/versions, tables/columns, row counts. The clause "Never the values" usefully separates it from value-returning siblings like query or panel_rows, though it never names an explicit alternative such as history or sent_to_ai.

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?

The parenthetical "(for 'what did my AI see?')" gives an explicit intent-based trigger an agent can match against a user question. There is no statement of when not to use it or which sibling covers adjacent needs, so guidance is clear but not exhaustive.

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