ShortsIntel

List trackers

list_trackers

Read-onlyIdempotent

Use when you need the Customer's Trackers, with state, kind and next cycle time, e.g. to find a tracker_id. Not for one Tracker's detail or sample: use get_tracker. Not for what changed: use get_changes. Price: Free. Filter by state or kind; next_cursor pages.

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

Input Schema

Name	Required	Description	Default
`kind`	No
`limit`	No
`state`	No
`cursor`	No

Output Schema

Name	Required	Description	Default
`items`	No
`next_cursor`	No	Pass back as `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026
- changedOutput schema / properties / items / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
- removedOutput schema / properties / items / items / properties
```
Removed value: -{}
```

Changed1 schema field changedNov 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "items": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "description": "Pass back as `cursor`.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful context beyond that: returned fields, filtering, pagination via next_cursor, and that the tool is free to use. It does not explain edge cases such as empty results or ordering, which keeps it from a 5.

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?

Very compact and front-loaded: the use case comes first, exclusions come next, and pricing and filtering notes follow. Every sentence adds practical information with no filler.

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?

With an output schema present and annotations covering safety, the description supplies the remaining decision-critical context: when to use it, when not to, filtering, pagination, and return fields. The missing limit explanation is minor relative to the overall completeness.

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 0%, so the description must compensate. It explains filtering by state or kind and pagination, but does not mention the limit parameter, and it says "next_cursor" while the schema parameter is named "cursor," leaving some ambiguity.

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?

States a specific verb and resource, "List trackers," and names the exact fields returned: state, kind, and next cycle time. It also gives the practical purpose, finding a tracker_id, which clearly distinguishes it from detail and change-oriented siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it and names the alternatives for adjacent needs: get_tracker for one tracker's detail/sample and get_changes for what changed. The filter and pagination guidance further clarifies invocation.

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

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

Resources

Need Help?