Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Get MCP change calls

get_mcp_change_calls
Read-only

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": {
      "agent_id": "<agent_id>",
      "change_id": "<change_id>"
    },
    "name": "get_mcp_change_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax calls to return (default 100, max 200).
offsetNoCalls to skip from the start of the burst (default 0). When `has_more` is True, re-call with offset += limit.
agent_idYesID of the agent the change was made to.
change_idYesThe change's id: the `id` of a `get_agent_details` `mcp_changes` entry, also shown as `(change N)` in the agent's Recent Activity.
on_behalf_ofNoA teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. Changed1 schema field changed
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds genuinely new behavior: results are ordered oldest first, paging is bounded and signaled via `has_more`, and the data originates from third-party MCP clients outside Sliq. It also embeds a returns block, though it doesn't mention rate limits or what happens for a change with no recorded calls.

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?

The summary is front-loaded with the core action, then the discriminating detail and example, and the separate returns block keeps return values out of the prose. The XML-style wrapper tags are slightly heavier than needed, but no sentence is 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?

For a read tool with no output schema, the description supplies the return shape, field names, ordering, and pagination protocol, which is everything an agent needs to call it correctly and to page through results. Pagination behavior is covered jointly by the description and schema, leaving no material gap.

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%, so every parameter including `agent_id`, `change_id`, `limit`, `offset`, and `on_behalf_of` is already documented in the schema. The description adds no parameter-level meaning beyond what the schema states (e.g., it doesn't clarify how the burst boundary is defined for paging). Baseline 3 applies.

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 names a specific verb and resource ('Read every call in one change made outside Sliq by ... MCP clients'), scopes it to external MCP activity, and states ordering ('oldest first'). It also spells out the distinction from the change summary that carries only the latest call's arguments, so an agent can tell exactly which tool gets the full burst.

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 an explicit trigger condition with a concrete example ('when you need the others, e.g. every prospect an `update_prospect` burst edited'), which is a strong when-to-use signal. It doesn't state exclusions or name a sibling tool to avoid, so it stops short of full routing guidance.

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

All Sliq 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