Skip to main content
Glama

search_kills

Read-only

Search a CS2 match kill log by attacker, victim, weapon, round, headshot, wallbang, noscope, or through-smoke; all filters are optional and combined with AND.

Instructions

Search the kill log. All filters are optional and combined with AND.

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": {
      "match_id": "<match_id>"
    },
    "name": "search_kills"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
victimNo
weaponNoInternal name: ak47, awp, deagle, knife…
noscopeNo
attackerNo
headshotNo
match_idYes
wallbangNo
round_numberNo
through_smokeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this a safe, closed read (readOnlyHint=true, openWorldHint=false), and the description adds the useful behavioral fact that filters are ANDed. It says nothing about pagination, the default limit of 60 or the cap at 300, or ordering of results, all of which matter for a log search.

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?

Two short, front-loaded sentences with no filler. The brevity is efficient rather than padded, though it shades into under-specification given ten parameters.

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?

With ten parameters, 10% schema coverage and no output explanation needed (an output schema exists), the description should explain filter semantics and the required match scope. Instead it omits the required parameter and leaves nine undocumented filters unexplained, which is thin for a tool of this complexity.

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 10% (only weapon is documented), so the description carries most of the burden and largely fails. It does not explain whether victim/attacker take player names or IDs, what round_number refers to, or what the boolean flags noscope/headshot/wallbang mean in combination, adding essentially nothing beyond AND semantics.

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?

"Search the kill log" gives a specific verb plus resource, so an agent immediately knows the domain of the tool. It stops short of differentiating from any related retrieval tool, but no sibling in the list clearly overlaps with kill-level search.

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 guidance is "All filters are optional and combined with AND", which implies filters narrow results but never says when to reach for this tool or what to do instead. Worse, the claim that all filters are optional conflicts with the schema, where match_id is required, so the statement actively misleads an agent about a mandatory argument.

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