Skip to main content
Glama

Complaint Recall Risk Tool

complaint-recall-risk
Read-only

Lists complaint and recall risk records for the authenticated workspace without exposing private operational notes. Use to inspect complaint and recall risks in the connected business. Returns query, count, total, risk_records, summary, scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "complaint-recall-risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum records to return.
queryNoJob title, customer name, or technician name.
statusNoRisk state; defaults to open.

Output Schema

NameRequiredDescriptionDefault
countYesCount for the returned result.
queryYesQuery used or returned by this tool.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
totalYesTotal for the returned result.
summaryYesSummary metadata; empty collections retain their existing JSON array representation.
risk_recordsYesBounded risk records records returned by this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Count for the returned result.",
      +      "type": "integer"
      +    },
      +    "query": {
      +      "description": "Query used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "risk_records": {
      +      "description": "Bounded risk records records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "summary": {
      +      "description": "Summary metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "total": {
      +      "description": "Total for the returned result.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "query",
      +    "count",
      +    "total",
      +    "risk_records",
      +    "summary",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral trait beyond them: private operational notes are withheld from the output, which tells the agent results are intentionally redacted. It omits pagination behavior and any note about how defaults (status=open, limit=20) affect what comes back.

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?

Three sentences, but the first ('Lists complaint and recall risk records') and second ('Use to inspect complaint and recall risks') restate the same fact. The final sentence enumerates return keys that the output schema already declares, which is filler rather than front-loaded value.

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

Completeness3/5

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

For a read-only, zero-required-parameter list tool with a full output schema and complete parameter docs, the description covers purpose, privacy behavior, and scope adequately. It leaves gaps on pagination, default status filtering effects, and how the returned 'summary'/'risk_records' relate to each other, so it is adequate but not thorough.

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 limit, query, and status are fully documented in structured fields, setting the baseline at 3. The description adds no syntax, format, or matching semantics for the query string beyond what the schema says. The trailing field list ('query, count, total...') describes returns, not inputs, so it does not compensate.

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?

States a clear verb+resource: lists complaint and recall risk records scoped to the authenticated workspace. The scope qualifier ('for the authenticated workspace') is specific. It does not differentiate from the sibling routing-driving-risk tool, which is a different risk-listing surface, so differentiation is left to inference.

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

Usage Guidelines3/5

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

'Use to inspect complaint and recall risks in the connected business' implies when to reach for it, but gives no when-not conditions, no prerequisites, and no pointer to the sibling risk tools. An agent gets a general sense of intent but nothing that resolves tool choice.

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