Skip to main content
Glama
io.github.ryanmat/logicmonitor

io.github.ryanmat/logicmonitor

by ryanmat

get_api_tokens

Read-onlyIdempotent

List API tokens, optionally filtered by user ID, with limit and offset pagination to support token audits and access reviews.

Instructions

List API tokens

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
admin_idNoUser ID whose tokens to list (omit for all tokens)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Pagination offset",
      +  "type": "integer"
      +}
  2. Changed1 schema field changedv4.2.1
    • addedInput schema / properties / admin_id
      Added value: +{
      +  "description": "User ID whose tokens to list (omit for all tokens)",
      +  "type": "integer"
      +}
  3. First observedv4.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — no note on pagination defaults, result ordering, or whether tokens/secrets are redacted in the response, which matters for a credential-listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words with zero filler and the key concept front-loaded, so nothing is wasted. But the brevity tips into under-specification — there is no room left for the scoping or pagination cues an agent would benefit from.

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?

With no output schema, the description is the only place to learn what a token record contains, yet it says nothing about return shape or whether secrets are exposed. For a credential-listing tool with pagination parameters, this leaves an agent without enough context to call it confidently.

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%, with limit, offset, and admin_id each documented, so the baseline of 3 applies. The description adds no meaning beyond the schema, such as a recommended page size or the effect of admin_id scoping on result volume.

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 and resource ('List API tokens'), so an agent immediately knows it retrieves a collection rather than a single token. It does not, however, distinguish itself from the sibling get_api_token (singular), leaving the collection-vs-single-token choice to inference from the name 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?

There is no when-to-use guidance at all: no statement about when to call this instead of get_api_token, and no mention that omitting admin_id returns the full token list (that fact lives only in the schema). The agent must derive usage entirely from the tool name.

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

Deploy Server

Other Tools