Skip to main content
Glama

Buyer search run summary

exim__run__summary
Read-onlyIdempotent

Returns the criteria, timing, company totals and priority breakdown of a buyer search run. Use it to report on or repeat a finished run.

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": {
      "runId": "<runId>"
    },
    "name": "exim__run__summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun UUID; finished runs preferred.

Output Schema

NameRequiredDescriptionDefault
dataYes
statsNo
_debugNo
summaryYes
warningsNo
nextActionsYes
correlationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / data / properties / context / anyOf
      Previous value: -[
      -  {
      -    "$ref": "#/$defs/value2"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "anyOf": [
      +      {
      +        "$ref": "#/$defs/value2"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  {
      +    "additionalProperties": true,
      +    "properties": {
      +      "referenced": {
      +        "type": "boolean"
      +      },
      +      "rowCount": {
      +        "type": "integer"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "referenced",
      +      "rowCount",
      +      "url"
      +    ],
      +    "type": "object"
      +  }
      +]
    • changedOutput schema / properties / data / properties / items / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "$ref": "#/$defs/value0"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "$ref": "#/$defs/value0"
      +        },
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "exportUrl": {
      +              "type": "string"
      +            },
      +            "payloadBytes": {
      +              "type": "integer"
      +            },
      +            "rowCount": {
      +              "type": "integer"
      +            },
      +            "token": {
      +              "type": "string"
      +            },
      +            "url": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "exportUrl",
      +            "payloadBytes",
      +            "rowCount",
      +            "token",
      +            "url"
      +          ],
      +          "type": "object"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Added
  3. Removed
  4. Added
  5. Removed
  6. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the result includes criteria, timing, totals and a priority breakdown, but says nothing about behavior on unfinished or missing runs, which is the main edge case for this tool.

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

Conciseness5/5

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

Two sentences, zero filler: the return contents come first and the usage cue second. Nothing is redundant with the title or annotations.

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?

An output schema exists, so return values need no explanation, and a single-parameter read-only tool needs little more. The only real omission is routing guidance relative to exim__run__status.

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?

With 100% schema coverage on a single runId parameter, the schema already documents the argument fully. The description reinforces the "finished run" expectation that the schema states as a preference, but adds no format, validation, or error semantics beyond it.

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 specific verb and resource ("Returns the criteria, timing, company totals and priority breakdown of a buyer search run") and enumerates the payload contents, so an agent knows exactly what comes back. It does not, however, distinguish itself from the close sibling exim__run__status, leaving the run-summary vs run-status split implicit.

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 it to report on or repeat a finished run" gives a usage context and an implicit precondition (run must be finished). No alternative is named, even though exim__run__status exists and is the obvious competing choice for run inspection, so the agent must infer which one to call.

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.