Skip to main content
Glama
Sign In

LiveCRM

by ai.livecrm
OverviewDiscussionsAdmin

List Queue History

list_queue_history
Read-only

Actions a person has already decided: executed, rejected and rolled back, newest first. THIS IS HOW YOU LEARN WHAT BECAME OF A PROPOSAL. A row you queued that is not in list_queue_actions is here, and the difference between rejected and executed is the answer to whether the change was wanted. A REJECTION IS DURABLE AND IS ALREADY ENFORCED: proposing the same change to the same record again is suppressed automatically, so re-proposing it is not merely rude but a no-op. Reading this before proposing is how you avoid asking twice. Scoped to one connection, like list_queue_actions.

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": {
      "connection_id": "<connection_id>"
    },
    "name": "list_queue_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows to return. Defaults to 25.
connection_idYesThe CRM connection. Call list_crm_connections first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many rows to return. Defaults to 50."New value: +"How many rows to return. Defaults to 25."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real behavior: result ordering, single-connection scoping, and the durable, server-enforced nature of rejections. It does not describe return format, pagination, or whether limit truncation is signaled, which is why it falls short of 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.

Conciseness3/5

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

The core scoping and sibling-routing information is front-loaded, which is good. However, the all-caps emphatic sentence largely restates the opening sentence, and the 'not merely rude but a no-op' clause restates the auto-suppression point already made, so roughly two of six clauses are 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?

For a simple two-parameter read tool with no output schema, the description conveys what rows appear, their ordering, their scope, and how the data should change the caller's next action. Nothing needed to invoke it correctly is missing.

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 both connection_id and limit documented in the schema, so the baseline is 3. The description reinforces that results are scoped to one connection but adds no syntax, format, or edge-case meaning beyond what the schema already states.

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 resource and scope: actions a person has already decided, enumerated as executed/rejected/rolled back, ordered newest first. It explicitly distinguishes itself from the sibling list_queue_actions by describing their complementary relationship (a queued row not in list_queue_actions is here). An agent can select between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use rule: read this before proposing to avoid asking twice. It also names the alternative (list_queue_actions) and the condition that separates them, and warns that re-proposing a rejected change is a suppressed no-op, which is actionable guidance rather than vague context.

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

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