Skip to main content
Glama

Kema Invoice

by com.kema-studio
OverviewDiscussionsAdmin

List MCP activity

list_mcp_activity
Read-only

The tenant's recent agent activity log: one entry per successful MCP tool call (tool name, related invoice number when known, timestamp). Newest first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of entries to return (1-50). Default 20.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesActivity entries, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Default 20."New value: +"Maximum number of entries to return (1-50). Default 20."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "items": {
+      "description": "Activity entries, newest first.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "created_at": {
+            "description": "Call timestamp (ISO 8601).",
+            "type": "string"
+          },
+          "invoice_number": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Related document number when the result carried one."
+          },
+          "tool_name": {
+            "description": "MCP tool that was called.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "tool_name",
+          "invoice_number",
+          "created_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The readOnlyHint annotation covers side-effect transparency, and the description adds that only successful calls are logged. It does not mention error handling or edge cases, but the annotation suffices for this read-only operation.

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?

The description is a single, focused sentence with no redundant information. It efficiently conveys the tool's purpose and output format.

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?

For a simple read-only log tool, the description is complete: it explains what entries look like and the ordering (newest first). The output schema is present, so no additional context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, limit, is fully described in the schema with constraints (1-50) and a default (20). The schema coverage is 100%, providing complete semantic clarity for the caller.

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?

The description clearly states the tool's function: listing the tenant's recent agent activity log. It specifies the resource (MCP tool calls) and distinguishes it from sibling tools that perform other operations.

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?

The description implies usage for auditing or reviewing agent actions, but does not explicitly state when to use it versus alternatives. Since no direct alternative exists among the sibling tools, the guidance is adequate but not fully explicit.

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

All Kema Invoice toolsInspect
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