Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Show API Key Activity

activity
Read-onlyIdempotent

Review API key requests and hourly read counts to audit account actions, filter by key, action, outcome, or date, and spot refused requests or errors.

Instructions

Show what this account's API keys did, newest first: every key of the account, including the one this agent uses, as the console's API keys page shows under Activity. kind "actions" lists each request that changed something, ran a check or an estimate, revealed a machine login or issued an install command, with its result. action is a name such as "pod.create", "storage.delete" or "machine.maintenance.schedule" (estimates end in ".estimate" and change nothing); outcome is "accepted", "refused" (error_title says why) or "error"; operation_id is set only for writes the server deduplicates (null otherwise), and replayed true means a retry got the first answer back instead of acting again. source, resource_id, machine_id, workspace and operation_id are what the calling client sent; the key is what identifies who sent the request. "reads" lists read requests as hourly counts (UTC) per key, source and kind of resource, without a total; the current hour can lag by a few seconds. Request contents are never recorded. key keeps one key's activity: a key_id from these results. For actions, outcome keeps one result and action keeps one action, or every action under a prefix ending in "." ("machine." for every machine action). since and until are dates in YYYY-MM-DD (UTC; until includes that whole day) or ISO 8601 times. The default is the last 30 days; one call covers at most 180 days, which is how long activity is kept. key_revoked true means that key has been revoked or deleted since. If the user doesn't recognize an action, tell them: they can revoke the key in the console.

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

Input Schema

NameRequiredDescriptionDefault
keyNo
kindNoactions
limitNo
sinceNo
untilNo
actionNo
cursorNo
outcomeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial context beyond that: request contents are never recorded, retention is 180 days, the default window is 30 days, "reads" can lag a few seconds in the current hour, `operation_id` is non-null only for server-deduplicated writes, and `replayed` means a retry returned the first answer rather than acting again. The `key_revoked` semantics and the revocation advice are extra operational context an agent would otherwise have to guess.

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?

Front-loaded: the first sentence gives purpose, ordering and scope before any detail, and parameters are marked with backticks so they are scannable. It is long and dense, with several multi-clause sentences (the `kind`/`action`/`outcome`/`operation_id` block) that could be split, but nearly every clause carries distinct semantics rather than filler.

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

Completeness4/5

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

An output schema exists, so the description need not explain return shape, and it correctly spends its words on semantics the schema cannot convey: retention limits, timestamp formats, deduplication flags, and the difference between action and read modes. The missing piece is pagination behavior for `limit`/`cursor`, which matters for a potentially large audit listing.

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 description coverage is 0%, so the description carries the burden, and it does so for most parameters: `key` (a key_id from prior results), `kind`, `action` with the prefix convention ("machine." matches every machine action) and the .estimate caveat, `outcome` values (accepted/refused/error), `since`/`until` formats (YYYY-MM-DD UTC, inclusive day, ISO 8601, 30-day default, 180-day cap). However `limit` and `cursor` — the pagination controls — are never mentioned, which is a real gap for an 8-parameter list tool.

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 ('Show what this account's API keys did, newest first') and anchors it to a known surface ('the console's API keys page shows under Activity'). This clearly separates it from sibling key-management tools such as access_keys, create_access_key or revoke_access_key, which operate on keys rather than reporting what they did.

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?

Gives concrete when-to-use guidance by splitting the two modes: `kind` "actions" for state-changing requests, checks, estimates, machine logins and install commands; "reads" for hourly read counts. It also prescribes the agent's next move ('If the user doesn't recognize an action, tell them: they can revoke the key in the console'). It stops short of naming sibling tools to route away from (e.g. logs or access_keys), so no explicit exclusion is stated.

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