Skip to main content
Glama

List company-owned cases or conversations with emotion filters (sentiment: happy, neutral, upset, angry, sad, mixed or unknown), a customer filter (customer: paid for a captured or authorized live payment, no_purchase for a matched contact who has not paid, unmatched for an unknown sender), ordering (sort, including customer_message for the latest customer message first), page size, coverage and a cursor

summer_cases_list
Read-onlyIdempotent

List company-owned cases or conversations with emotion filters (sentiment: happy, neutral, upset, angry, sad, mixed or unknown), a customer filter (customer: paid for a captured or authorized live payment, no_purchase for a matched contact who has not paid, unmatched for an unknown sender), ordering (sort, including customer_message for the latest customer message first), page size, coverage and a cursor. Operational rows include conversationSentiment (label, confidence, evidence references, source, assessed_at and pending freshness). Operational filters require the company's operational connection; Messenger-only results include coverage limits.

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>",
      "environment": "<environment>"
    },
    "name": "summer_cases_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
laneNo
mineNo
planNo
sortNo
limitNo
cursorNo
statusNo
companyYesSummer company ID
pastSlaNo
sandboxNo
snoozedNoActive cases leave out snoozed cases: not waiting on the team, with a follow-up still in the future. true lists only snoozed cases.
autonomyNo
categoryNo
customerNo
internalNo
languageNo
severityNo
attentionNoOnly active cases with a reply owed, a plan to review, or blocked, failed, stale or uncertain work. Hides queued investigations and ongoing approved execution, even when a reply is owed. Includes ready plans and blocked or uncertain work. Hides snoozed, waiting and completed cases without a current action. Follow-up dates alone do not qualify; use followUps for scheduled checks.
followUpsNo
sentimentNo
unmatchedNo
dismissalsNo
reviewMineNo
workstreamNo
environmentYesEnvironment that owns the resource
escalationsNo
responseDueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / attention / description
      Previous value: -"Only active cases with a reply owed, a plan to review, or blocked, failed, stale or uncertain work. Hides snoozed, waiting and completed cases without a current action. Follow-up dates alone do not qualify; use followUps for scheduled checks."New value: +"Only active cases with a reply owed, a plan to review, or blocked, failed, stale or uncertain work. Hides queued investigations and ongoing approved execution, even when a reply is owed. Includes ready plans and blocked or uncertain work. Hides snoozed, waiting and completed cases without a current action. Follow-up dates alone do not qualify; use followUps for scheduled checks."
  2. Changed1 schema field changed
    • addedInput schema / properties / attention
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Only active cases with a reply owed, a plan to review, or blocked, failed, stale or uncertain work. Hides snoozed, waiting and completed cases without a current action. Follow-up dates alone do not qualify; use followUps for scheduled checks."
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / snoozed
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Active cases leave out snoozed cases: not waiting on the team, with a follow-up still in the future. true lists only snoozed cases."
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / customer
      Added value: +{
      +  "enum": [
      +    "paid",
      +    "no_purchase",
      +    "unmatched"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "priority",
      -  "newest",
      -  "oldest",
      -  "due",
      -  "activity",
      -  "autonomy_desc",
      -  "autonomy_asc"
      -]New value: +[
      +  "priority",
      +  "newest",
      +  "oldest",
      +  "due",
      +  "activity",
      +  "customer_message",
      +  "autonomy_desc",
      +  "autonomy_asc"
      +]
  5. Changed1 schema field changed
    • addedInput schema / properties / sentiment
      Added value: +{
      +  "enum": [
      +    "happy",
      +    "neutral",
      +    "upset",
      +    "angry",
      +    "sad",
      +    "mixed",
      +    "unknown"
      +  ],
      +  "type": "string"
      +}
  6. Changed21 schema fields changed
    • addedInput schema / properties / autonomy
      Added value: +{
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / category
      Added value: +{
      +  "maxLength": 80,
      +  "type": "string"
      +}
    • removedInput schema / properties / cursor / maxLength
      Removed value: -200
    • addedInput schema / properties / cursor / pattern
      Added value: +"^[1-9]\\d{0,5}$"
    • addedInput schema / properties / dismissals
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ]
      +}
    • addedInput schema / properties / escalations
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ]
      +}
    • addedInput schema / properties / followUps
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ]
      +}
    • addedInput schema / properties / internal
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ]
      +}
    • addedInput schema / properties / lane
      Added value: +{
      +  "enum": [
      +    "all",
      +    "customer_request",
      +    "proactive_issue",
      +    "source_review"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / language
      Added value: +{
      +  "enum": [
      +    "en",
      +    "es",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / mine
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ]
      +}
    • addedInput schema / properties / pastSla
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ]
      +}
    • addedInput schema / properties / plan
      Added value: +{
      +  "enum": [
      +    "all",
      +    "ready"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / responseDue
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ]
      +}
    • addedInput schema / properties / reviewMine
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ]
      +}
    • addedInput schema / properties / sandbox
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ]
      +}
    • addedInput schema / properties / severity
      Added value: +{
      +  "enum": [
      +    "normal",
      +    "high",
      +    "urgent"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "enum": [
      +    "priority",
      +    "newest",
      +    "oldest",
      +    "due",
      +    "activity",
      +    "autonomy_desc",
      +    "autonomy_asc"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "open",
      -  "resolved",
      -  "all"
      -]New value: +[
      +  "open",
      +  "in_progress",
      +  "resolved",
      +  "closed",
      +  "active",
      +  "all"
      +]
    • addedInput schema / properties / unmatched
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ]
      +}
    • addedInput schema / properties / workstream
      Added value: +{
      +  "maxLength": 80,
      +  "type": "string"
      +}
  7. First observed

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavior: operational rows carry conversationSentiment with label, confidence, evidence references, source, assessed_at and pending freshness, and results degrade with coverage limits when only Messenger data is present — both are facts an agent cannot get from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The first sentence is a run-on enumeration that largely duplicates the title and restates enum values already in the schema, burying the two sentences that actually add value (sentiment payload and coverage limits). Nothing is front-loaded for scanning; the useful operational caveats sit at the tail.

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

Completeness2/5

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

For a 27-parameter list tool with no output schema and no annotation-level detail about returns, the description is thin: it never states the result shape, pagination/limit defaults, or what most filters mean. The sentiment-row note is helpful but does not cover the tool's surface area.

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

Parameters2/5

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

Schema description coverage is only 15% across 27 parameters, so the description carries most of the burden. It explains the customer enum values precisely and names customer_message in sort, but leaves lane, mine, plan, status, pastSla, autonomy, category, severity, internal, language, followUps, unmatched, dismissals, reviewMine, workstream, escalations, responseDue and the cursor mechanics undocumented in both places.

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 opening clause states a specific verb and resource ('List company-owned cases or conversations') and names the two axes of filtering that make it distinctive (sentiment, customer). It does not distinguish it from close siblings such as summer_cases_search or summer_messenger_conversations_list, so an agent must infer the boundary, but the purpose itself is unambiguous.

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

Usage Guidelines2/5

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

The only conditional guidance is 'Operational filters require the company's operational connection', which is a prerequisite rather than a when-to-use rule. Nothing tells the agent when to choose this over summer_cases_search, summer_cases_get, summer_cases_account, or summer_messenger_conversations_list, and no exclusions are stated.

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.