OneUptime

Count Logs

count_logs

Read-only

Count Logs telemetry, all of it or what a filter matches. Prefer to filter on time.

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

Input Schema

Name	Required	Description	Default
`query`	No	A field's value, or an operator such as {"_type":"GreaterThan","value":...}. Fields and operators: oneuptime_describe_resource.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / query / description

Previous value: -"Filter. Each field takes a value (exact match) or an operator, such as {\"_type\":\"GreaterThan\",\"value\":...}. Fields and operators: oneuptime_describe_resource."New value: +"A field's value, or an operator such as {\"_type\":\"GreaterThan\",\"value\":...}. Fields and operators: oneuptime_describe_resource."

Changed3 schema fields changedNov 4, 2026

changedInput schema / properties / query / additionalProperties
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / query / description

Previous value: -"Optional filter criteria. Each field accepts a direct value (exact match) or an operator object {\"_type\": \"<Operator>\", \"value\": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween (numbers/dates), Search (partial text), Includes (array of values). Example — items from the last 24 hours: {\"createdAt\": {\"_type\": \"GreaterThan\", \"value\": \"2026-01-01T00:00:00.000Z\"}}."New value: +"Filter. Each field takes a value (exact match) or an operator, such as {\"_type\":\"GreaterThan\",\"value\":...}. Fields and operators: oneuptime_describe_resource."

removedInput schema / properties / query / properties

Removed value: -{
-  "_id": {
-    "description": "_id field",
-    "type": "string"
-  },
-  "attributeKeys": {
-    "description": "attributeKeys field",
-    "type": "string"
-  },
-  "attributes": {
-    "description": "attributes field",
-    "type": "string"
-  },
-  "body": {
-    "description": "body field",
-    "type": "string"
-  },
-  "containerEntityKey": {
-    "description": "containerEntityKey field",
-    "type": "string"
-  },
-  "createdAt": {
-    "description": "createdAt field",
-    "type": "string"
-  },
-  "droppedAttributesCount": {
-    "description": "droppedAttributesCount field",
-    "type": "string"
-  },
-  "entityKeys": {
-    "description": "entityKeys field",
-    "type": "string"
-  },
-  "flags": {
-    "description": "flags field",
-    "type": "string"
-  },
-  "hostEntityKey": {
-    "description": "hostEntityKey field",
-    "type": "string"
-  },
-  "k8sClusterEntityKey": {
-    "description": "k8sClusterEntityKey field",
-    "type": "string"
-  },
-  "k8sNodeEntityKey": {
-    "description": "k8sNodeEntityKey field",
-    "type": "string"
-  },
-  "k8sPodEntityKey": {
-    "description": "k8sPodEntityKey field",
-    "type": "string"
-  },
-  "observedTimeUnixNano": {
-    "description": "observedTimeUnixNano field",
-    "type": "string"
-  },
-  "primaryEntityId": {
-    "description": "primaryEntityId field",
-    "type": "string"
-  },
-  "primaryEntityType": {
-    "description": "primaryEntityType field",
-    "type": "string"
-  },
-  "projectId": {
-    "description": "projectId field",
-    "type": "string"
-  },
-  "retentionDate": {
-    "description": "retentionDate field",
-    "type": "string"
-  },
-  "serviceEntityKey": {
-    "description": "serviceEntityKey field",
-    "type": "string"
-  },
-  "sessionId": {
-    "description": "sessionId field",
-    "type": "string"
-  },
-  "severityNumber": {
-    "description": "severityNumber field",
-    "type": "string"
-  },
-  "severityText": {
-    "description": "severityText field",
-    "type": "string"
-  },
-  "spanId": {
-    "description": "spanId field",
-    "type": "string"
-  },
-  "time": {
-    "description": "time field",
-    "type": "string"
-  },
-  "timeUnixNano": {
-    "description": "timeUnixNano field",
-    "type": "string"
-  },
-  "traceId": {
-    "description": "traceId field",
-    "type": "string"
-  }
-}

First observedOct 19, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. The description adds that counting can run over the entire log set, and the 'prefer to filter on time' hint implicitly signals that unfiltered counting may be costly. It still omits return shape (single total vs. grouped/bucketed counts) and any default time window.

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?

Two short sentences, front-loaded with the verb and scope, with zero filler. The terseness borders on under-specification rather than verbosity, so it is efficient but leaves the reader wanting more.

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

Completeness2/5

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

The tool takes a free-form nested query object and has no output schema, yet the description never states what is returned (a count value, possibly bucketed) or how unfiltered/very broad counts behave. For a telemetry-count tool with an open-ended filter object, more guidance is needed.

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% and the query parameter's description already explains the field/operator shape and points to oneuptime_describe_resource. The description adds only the semantics that omitting query means 'all of it' and a preference for time fields, without naming the time field or explaining how filters combine.

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 ('Count Logs telemetry') and clarifies scope as either the full dataset or a filter-matched subset. It is understandable in isolation, but it never distinguishes itself from close siblings such as count_monitor_logs or list_logs, leaving the agent to infer the boundary.

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?

'Prefer to filter on time' is a weak hint about how to scope the query, but there is no guidance on when to choose this over list_logs (fetch entries vs. count them) or count_monitor_logs (monitor-scoped logs). No when-not-to-use or prerequisite conditions are given.

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

All OneUptime 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.