Skip to main content
Glama

Change log

get_events
Read-only

The changes made through API keys and connected apps, newest first: what was done (such as trade.record or alert.delete), when, to which stock, through which key or app, and a summary of what changed. Changes made on the website itself are not in it.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size. Default 25.
sinceNoOnly changes after this time (ISO 8601).
untilNoOnly changes up to this time (ISO 8601).
actionNoOne action, or several separated by commas, such as trade.record,trade.delete.
offsetNoWhere the page starts; take next_offset from the previous answer. Default 0.
tickerNoFor example 0700.HK or 700 (hk), AAPL (us), 600519.SS or 600519 (cn).

Output Schema

NameRequiredDescriptionDefault
errorNo
limitNo
totalNo
eventsNo
offsetNo
warningsNo
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds real behavioral context beyond that: the ordering guarantee (newest first) and the exclusion of website-originated changes, which is the kind of emptiness-invoking constraint an agent cannot get from annotations. It does not discuss pagination behavior or volume, which is a minor residual gap.

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?

Effectively one long but well-structured sentence that front-loads the identity (what was done, when, to which stock, through which key) before the exclusion clause. No filler or marketing language. It could be split for readability, but nothing is redundant.

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?

An output schema exists, so return shape need not be explained, yet the description still summarizes what an entry contains, which helps an agent judge relevance before calling. With six optional parameters and full schema coverage, the definition covers scope, ordering, and exclusions adequately. The only shortfall is the absence of any hint about expected result volume or how the log relates to sibling retrieval tools.

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 coverage is 100%, with every parameter already documented including ISO 8601 formats, action syntax, ticker examples, and the offset/next_offset paging convention, so the baseline is 3. The description reinforces the domain of the `action` filter by citing example values (trade.record, alert.delete) but adds no format or constraint detail beyond the schema. Paging semantics and the interplay of offset with 'newest first' ordering are left to the schema.

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 names a specific resource (the change log) and enumerates its contents — action, timestamp, stock, key/app, and change summary — plus a clear ordering rule ('newest first'). It is not tautological. What keeps it from a 5 is that it never names or contrasts a sibling, so an agent must infer for itself whether get_journal or get_journal_stats overlaps with this log.

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?

There is a genuine negative scope statement — changes made on the website are excluded — which tells the agent when this tool will return nothing useful. However, there is no explicit when-to-use guidance, no mention of prerequisites (e.g., API key required to produce any entries), and no routing to alternatives among the many sibling read tools. Usage is implied rather than directed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.