Skip to main content
Glama

ExducerAI GPU cloud

Deployment events

get_deployment_events
Read-onlyIdempotent

The state changes of a deployment, oldest first, each with its reason, actor and time. Read this to learn why a deployment failed, ended or is waiting.

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": {
      "id": "<id>"
    },
    "name": "get_deployment_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe deployment id (rnt_… on a live key, snd_… in the sandbox).
limitNoHow many events.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the operation read-only, idempotent and non-destructive. The description adds useful behavioral detail by describing the returned events, their fields and ordering, though it does not address pagination or truncation behavior when the limit is reached.

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?

The description is two focused sentences with no wasted wording. It front-loads what the tool returns, then supplies the diagnostic use case.

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?

For a simple two-parameter read tool without an output schema, the description gives enough detail about returned content and ordering. The main gap is that it does not clarify pagination or what happens when more events exist than the limit allows.

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 description coverage is 100%, so the schema already documents both the deployment id and the limit parameter. The description does not add meaning beyond the schema for either parameter, which is the baseline when schema coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: the state changes of a deployment, ordered oldest first, with reason, actor and time. It clearly distinguishes this event-history tool from general deployment retrieval by focusing on state changes and diagnostic use.

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?

It gives clear usage context: read this to learn why a deployment failed, ended or is waiting. It does not explicitly name alternatives or when not to use it, so it falls short of the top score for guidance.

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.

Resources