Algenta MCP Server

ingest_metering_events

Ingest one batch of execution-analytics events from a managed runtime that explicitly enabled control-plane sync. This endpoint is analytics-only: received events are counted for dashboards and structured-logged, never used for billing or quota enforcement, and self-hosted Algenta profiles never call it automatically. Every event field is optional; events without a timestamp count toward the current billing month. An empty events list fails with empty_events. Returns accepted (event count) and the primary billing_period.

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": {
      "device_id": "<device_id>",
      "events": "<events>"
    },
    "name": "ingest_metering_events"
  }
}

Input Schema

Name	Required	Description	Default
`events`	Yes	Analytics events; every field below is optional.
`device_id`	Yes	Managed-runtime device id that produced the events.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 23, 2026
- addedInput schema / properties / device_id / description
```
Added value: +"Managed-runtime device id that produced the events."
```
- addedInput schema / properties / events / description
```
Added value: +"Analytics events; every field below is optional."
```
- addedInput schema / properties / events / items / properties / engine_used / description
```
Added value: +"Compute engine that executed the call."
```
- addedInput schema / properties / events / items / properties / event_type / description
```
Added value: +"Event kind label, e.g. execution."
```
- addedInput schema / properties / events / items / properties / function / description
```
Added value: +"Function within the module that ran."
```
- addedInput schema / properties / events / items / properties / latency_ms / description
```
Added value: +"Observed execution latency in milliseconds."
```
- addedInput schema / properties / events / items / properties / module / description
```
Added value: +"Runtime module that ran."
```
- addedInput schema / properties / events / items / properties / request_id / description
```
Added value: +"Caller-side request id for correlation."
```
- addedInput schema / properties / events / items / properties / success / description
```
Added value: +"Whether the execution succeeded."
```
- addedInput schema / properties / events / items / properties / timestamp / description
```
Added value: +"Unix timestamp of the event; determines its billing period."
```
First observedJul 12, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With all annotations false, the description carries the full burden of behavioral disclosure and does so thoroughly. It reveals that events are analytics-only, never affect billing/quota, that every field is optional, that missing timestamps default to the current billing month, that an empty list fails with empty_events, and that the return includes accepted count and billing_period. This goes well beyond the annotations.

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 dense but every sentence contributes: purpose, analytics-only clarification, field optionality/timestamp default, failure condition, and return values. It is front-loaded with the core purpose and contains no filler or redundant restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no output schema and minimal annotations, the description covers everything needed to call it correctly: the exact source condition, how events are handled, timestamp defaulting, the empty-events failure mode, and the return payload. It is complete for an agent executing this tool.

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%, so the baseline is 3. The description adds value beyond the schema by explaining that events without a timestamp count toward the current billing month and that an empty events list fails with empty_events, giving the agent important behavioral meaning for the events parameter.

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 opens with a specific verb and resource: 'Ingest one batch of execution-analytics events'. It clearly scopes the source to managed runtimes with control-plane sync enabled and explicitly distinguishes the endpoint as analytics-only, never used for billing or quota enforcement, which separates it from the many sibling tools like get_usage, get_analytics, and get_billing_info.

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 explicit when-to-use context (managed runtime with control-plane sync) and strong when-not signals (self-hosted profiles never call it automatically, and it is never used for billing/quota enforcement). However, it does not name any alternative tool by name, so it falls short of a full 5.

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

All Algenta MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.