Skip to main content
Glama

Summarize matches

summarize_matches
Read-only

Get match counts by triage status, kind and verdict (by_verdict counts completed assessments across every status), plus how many are new (undecided inbox matches first found by the latest completed scan of their kind) and how many scans are active (active_scans). It gives an overview of the current state.

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": "summarize_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoLimits the counts to one match kind.
monitor_idNoLimits the counts to one monitor.

Output Schema

NameRequiredDescriptionDefault
newYes
totalYes
by_kindYes
by_statusYes
by_verdictYes
active_scansYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "domain",
      -  "trademark",
      -  "app"
      -]New value: +[
      +  "domain",
      +  "trademark",
      +  "app",
      +  "search_ad"
      +]
    • addedOutput schema / properties / by_kind / properties / search_ad
      Added value: +{
      +  "type": "number"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / by_verdict
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "clear": {
      +      "type": "number"
      +    },
      +    "inconclusive": {
      +      "type": "number"
      +    },
      +    "low": {
      +      "type": "number"
      +    },
      +    "violation": {
      +      "type": "number"
      +    },
      +    "warning": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "violation",
      +    "warning",
      +    "low",
      +    "clear",
      +    "inconclusive"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "total",
      -  "by_status",
      -  "by_kind",
      -  "new",
      -  "active_scans"
      -]New value: +[
      +  "total",
      +  "by_status",
      +  "by_kind",
      +  "by_verdict",
      +  "new",
      +  "active_scans"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Restrict to one match kind."New value: +"Limits the counts to one match kind."
    • changedInput schema / properties / monitor_id / description
      Previous value: -"Restrict to one monitor."New value: +"Limits the counts to one monitor."
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish this as a read-only, closed-world, non-destructive tool. The description goes beyond that by defining the non-obvious semantics of 'by_verdict', 'new', and 'active_scans', which an agent needs in order to interpret the output correctly.

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?

It is a single dense sentence that is front-loaded with the core behavior and uses parentheses to define terms without wasting words. The nested definitions make it slightly heavy but every clause earns its place.

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

Completeness4/5

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

With annotations covering safety, an output schema covering return structure, and fully documented parameters, the description supplies the remaining critical context: how counts are categorized and what 'new' means. Only explicit sibling-routing guidance 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%, and both kind and monitor_id are documented in the schema as count limiters. The description adds no parameter-level detail beyond what the schema already provides, so the baseline of 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 uses a specific verb ('Get match counts') and resource, and enumerates the dimensions returned (triage status, kind, verdict, new, active_scans). It implicitly distinguishes itself from list_matches by being an aggregate overview, though it does not name a sibling explicitly.

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?

The phrase 'It gives an overview of the current state' implies when the tool is appropriate, but there is no explicit guidance on when to prefer it over list_matches or when not to use it. Usage is inferable rather than 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.

Resources