Skip to main content
Glama

Count Data Store Access Entries

count_data_store_access_entries
Read-only

Count Data Store Access Entries, all or those a filter matches.

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_data_store_access_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoA 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.

  1. Changed1 schema field changed
    • 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."
  2. Changed3 schema fields changed
    • changedInput schema / properties / query / additionalProperties
      Previous value: -falseNew value: +true
    • changedInput schema / properties / query / description
      Previous value: -"Optional filter criteria. If omitted, counts all Data Store Access Entries. 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": "Query operators for _id field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
      -    },
      -    "type": "object"
      -  },
      -  "accessKey": {
      -    "description": "Query operators for accessKey field of type Long Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "example_value_1"
      -    },
      -    "type": "object"
      -  },
      -  "accessLevel": {
      -    "description": "Query operators for accessLevel field of type Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "John Doe"
      -    },
      -    "type": "object"
      -  },
      -  "createdAt": {
      -    "description": "Query operators for createdAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "2023-01-01T00:00:00.000Z"
      -    },
      -    "type": "object"
      -  },
      -  "dataStoreId": {
      -    "description": "Query operators for dataStoreId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
      -    },
      -    "type": "object"
      -  },
      -  "deletedAt": {
      -    "description": "Query operators for deletedAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "2023-01-01T00:00:00.000Z"
      -    },
      -    "type": "object"
      -  },
      -  "firstSeenAt": {
      -    "description": "Query operators for firstSeenAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "2023-01-01T00:00:00.000Z"
      -    },
      -    "type": "object"
      -  },
      -  "grantedVia": {
      -    "description": "Query operators for grantedVia field of type Long Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "example_value_1"
      -    },
      -    "type": "object"
      -  },
      -  "isExternal": {
      -    "description": "Query operators for isExternal field of type Boolean. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": true
      -    },
      -    "type": "object"
      -  },
      -  "isPublic": {
      -    "description": "Query operators for isPublic field of type Boolean. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": true
      -    },
      -    "type": "object"
      -  },
      -  "isSeenInTraces": {
      -    "description": "Query operators for isSeenInTraces field of type Boolean. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": true
      -    },
      -    "type": "object"
      -  },
      -  "isUnused": {
      -    "description": "Query operators for isUnused field of type Boolean. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": true
      -    },
      -    "type": "object"
      -  },
      -  "lastSeenAt": {
      -    "description": "Query operators for lastSeenAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "2023-01-01T00:00:00.000Z"
      -    },
      -    "type": "object"
      -  },
      -  "lastUsedAt": {
      -    "description": "Query operators for lastUsedAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "2023-01-01T00:00:00.000Z"
      -    },
      -    "type": "object"
      -  },
      -  "principal": {
      -    "description": "Query operators for principal field of type Long Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "example_value_1"
      -    },
      -    "type": "object"
      -  },
      -  "principalName": {
      -    "description": "Query operators for principalName field of type Long Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "example_value_1"
      -    },
      -    "type": "object"
      -  },
      -  "principalType": {
      -    "description": "Query operators for principalType field of type Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "John Doe"
      -    },
      -    "type": "object"
      -  },
      -  "projectId": {
      -    "description": "Query operators for projectId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
      -    },
      -    "type": "object"
      -  },
      -  "updatedAt": {
      -    "description": "Query operators for updatedAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": "2023-01-01T00:00:00.000Z"
      -    },
      -    "type": "object"
      -  },
      -  "version": {
      -    "description": "Query operators for version field of type Number. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
      -    "example": {
      -      "_type": "EqualTo",
      -      "value": 50
      -    },
      -    "type": "object"
      -  }
      -}
  3. Changed1 schema field changed
    • addedInput schema / properties / query / properties / isUnused
      Added value: +{
      +  "description": "Query operators for isUnused field of type Boolean. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull",
      +  "example": {
      +    "_type": "EqualTo",
      +    "value": true
      +  },
      +  "type": "object"
      +}
  4. Added

TDQS

C2.9/5.0
Behavior2/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 safety is fully covered by structured data. The description adds nothing beyond that: no note on what the returned count represents (raw rows vs distinct stores), no indication of how nested query operators are evaluated, and no cost or limit caveats. It simply mirrors the title.

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?

One short sentence with the resource front-loaded and the two modes (all vs filtered) stated compactly; nothing is padded. It is terse to the point that it borders on restating the title, but there is no wasted wording.

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

Completeness3/5

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

This is a simple read-only tool with one optional parameter, and the annotations plus full schema coverage carry most of the burden. However, with no output schema the description should at least confirm the return is a numeric total, and it never distinguishes this from the count/list family of siblings.

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 nested query object's structure and the pointer to oneuptime_describe_resource are already documented. The description's phrase "those a filter matches" only confirms the parameter's role, adding no operator, field, or matching-semantics detail beyond 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 states a specific verb plus resource ("Count Data Store Access Entries") and adds scope ("all or those a filter matches"), so the agent knows this returns a tally rather than records. It does not name the obvious sibling list_data_store_access_entries, so the count-vs-list distinction must be inferred from the verb alone.

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?

"all or those a filter matches" only restates that the query parameter is optional; it says nothing about when to reach for this instead of list_data_store_access_entries or get_data_store_access_entry. There are no exclusions, prerequisites, or framing for totals versus paginated reads.

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.