Skip to main content
Glama

Get application timeline

get_application_timeline
Read-only

Get an Application's recorded history, newest first: created, setup PR merged, platform builds, deploy runs, PR/branch demo previews, and AI reviews, each with status and timestamp. Use this to answer what happened and when. Read-only.

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": {
      "application_id": "<application_id>"
    },
    "name": "get_application_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum events to return (default 60, max 100).
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation already declares safety, and 'Read-only' merely restates it. What does add value is the disclosure of ordering (newest first) and that each entry carries a status and timestamp, plus the enumerated event categories. However, it says nothing about completeness or truncation, which matters given the limit parameter defaults to 60.

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 its content, followed by the use case and the safety note. No filler or repetition; every clause contributes scope, ordering, or payload detail.

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 description carries the return-value burden and does so by naming the event categories and their per-entry fields (status, timestamp). The only material gap is the absence of any note about how many events come back by default or whether older history requires paging with the limit parameter.

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 100% and both parameters are fully documented in the schema, so the baseline is 3; the description earns one extra point by revealing the result ordering ('newest first'), a piece of semantics the schema does not express. It does not discuss the limit cap or default, but the schema already covers that.

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 ('Get an Application's recorded history') and enumerates the event types included (created, setup PR merged, platform builds, deploy runs, demo previews, AI reviews), which separates it from single-facet siblings like get_application_deployments or list_application_pull_request_reviews. It stops short of naming the near-neighbour 'resource_timeline' or any sibling explicitly, so the differentiation is by content rather than by routing.

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?

'Use this to answer what happened and when' gives an implied use case (historical/audit questions) but no when-not guidance, no prerequisites, and no pointer to alternative tools when the agent only wants deployments, reviews, or a non-application resource history. Usage is inferable but not 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.