Skip to main content
Glama

import_matches

Imports selected matches from a source for download and analysis, creating one job per match and reporting skipped existing or demo-less matches.

Instructions

Download and analyze matches from a source (see list_source_matches). Returns one job per match; wait with get_job, whose result carries the new match_id. Matches already imported or without a demo are reported in skipped.

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": {
      "source_id": "<source_id>",
      "remote_ids": "<remote_ids>"
    },
    "name": "import_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYes
remote_idsYes
auto_render_topNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare this is a non-read-only, non-destructive, closed-world operation; the description adds the async execution model (one job per match, poll with get_job, the new match_id arrives in the job result). It also discloses dedup/skip behavior ('already imported or without a demo are reported in skipped'), which is genuine behavioral context an agent cannot get from annotations.

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?

Three dense sentences, front-loaded with the action, then the async contract, then the edge-case outcome. No filler and no restatement of the tool name.

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 and the description still usefully explains the job handoff and the skipped-reporting outcome for a mutating, multi-item import. The only material omission is any hint about what auto_render_top controls, which matters for a tool with a 20-match batch limit.

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 0%, so the description carries the burden and only partially does: source_id is implied via list_source_matches and remote_ids is implied by 'one job per match'. The third parameter, auto_render_top, is never mentioned, and neither the 20-item cap on remote_ids nor the required-vs-optional split is clarified.

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?

Uses a specific verb pair ('Download and analyze') with a clear resource ('matches from a source') and points to list_source_matches for discovering the source. It is clearly distinct from the sibling it names, though it does not differentiate itself from import_demo.

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

Usage Guidelines4/5

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

Explicitly routes the agent to list_source_matches to obtain a source and to get_job to wait for completion, which is real when/how guidance. It stops short of stating exclusions or when to prefer import_demo over this tool for single-match imports.

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