Skip to main content
Glama

yeastar_audit_log

Read-onlyIdempotent

Retrieve the audit log of changes applied or failed through this server in reverse chronological order, with optional limits or filtering by change ID.

Instructions

Registro delle modifiche applicate (o fallite) tramite questo server, dalla più recente.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
change_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuine context beyond that: it records both successful and failed changes, and results come back most-recent-first. It says nothing about retention window, pagination, or how many entries exist overall.

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?

One short sentence, front-loaded with the resource and immediately followed by the ordering rule; no filler. It is arguably too terse rather than padded, which is a completeness issue rather than a conciseness one.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. What remains missing is the meaning of both input parameters and any pointer to the related pending-changes tool, leaving the agent to infer filtering behavior for a simple two-parameter read.

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% and neither of the two parameters (limit, change_id) is explained. The phrase 'dalla più recente' hints at ordering, which relates to limit, but the description never says that limit caps result count or that change_id filters to a single entry, so it fails to compensate for the coverage 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 resource and scope: a log of changes applied or failed through this server, ordered most-recent-first. That is far more informative than the bare name, but it does not distinguish it from the closely related sibling yeastar_pending_changes (pending vs. already-attempted changes), so an agent cannot fully disambiguate from the text alone.

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?

There is no when-to-use or when-not-to-use guidance. The description never says to consult this after an apply/cancel attempt, nor that yeastar_pending_changes should be used for not-yet-applied work. Usage is only inferable from the word 'audit log'.

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