Skip to main content
Glama

Company activity log

company_audit_list
Read-onlyIdempotent

The activity log of one of your companies (owners and admins only), newest first: who did what and when, on the website or through a connection. Only field names are listed, not values. Filter by action and date range. Pass nextCursor to get the next page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "company_audit_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO date or time, exclusive.
fromNoISO date or time, inclusive.
limitNoHow many rows (1-50).
actionNo
cursorNonextCursor from the previous page.
companyYesCompany ref (CO-XXXXXXXX) from company_list_mine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds genuinely new behavior: result ordering (newest first), the authorization prerequisite (owners and admins), and — most importantly — that only field names are returned, not values. It does not mention rate limits or retention windows, which keeps it below 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?

Front-loaded with the resource and scope, then audience restriction, then result shape, then filtering and pagination. Every clause carries information and none is redundant.

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 no output schema, the description compensates well by characterizing the return shape (who/what/when, field names only, newest first) and the pagination contract. Access restrictions and filtering behavior are also present, so an agent has enough to call this correctly.

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 83%, with the from/to inclusivity, limit bounds, action enum, and cursor already documented in the schema. The description only restates the filtering and cursor concepts without adding format or edge-case meaning, so the baseline 3 applies.

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 names a specific resource and scope — the activity log of one company, newest first, covering 'who did what and when' on the website or via a connection. That scope ('one of your companies') implicitly distinguishes it from the profile/security/portal activity siblings, but it never explicitly contrasts with them.

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?

It gives clear operational context: owners and admins only, filter by action and date range, and pass nextCursor for the next page. It does not state when to prefer this over the other *_activity_list tools, so routing is left partly to inference.

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.

Resources