Skip to main content
Glama

Check services I use for breaches

check_services
Read-onlyIdempotent

Given up to 10 companies or services a person uses, say for each whether Teollimi has a reported breach, how many, and the latest one with what leaked. Absence of a record does not mean the service was never breached.

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": {
      "services": "<services>"
    },
    "name": "check_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: ko (Korean), en (English) or ja (Japanese). Defaults to the query's language, else English.
servicesYesCompany or service names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's main contribution is epistemic: 'Absence of a record does not mean the service was never breached.' That caveat meaningfully changes how an agent should interpret and relay empty results. It also previews the per-service return content, though it says nothing about ordering, result size, or latency.

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 dense sentences with zero filler; the output shape is front-loaded and the important caveat is placed last for emphasis. Every clause carries information.

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 no output schema, the description does the work of explaining what comes back per service (yes/no, count, latest incident and leaked fields), which is the key gap it needed to fill. The lang parameter's default is handled in the schema. Minor omissions are ordering of results and what happens when fewer than 10 services are supplied, but nothing essential to a correct call 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 parameters are documented there, including the enum and default behavior for lang. The description reinforces the 10-item cap verbally but adds no format, matching, or disambiguation guidance for service names (e.g. aliases or case sensitivity), so baseline 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 gives a specific verb ('say for each whether') and resource ('companies or services a person uses'), and it even specifies the shape of the answer: breach presence, count, and latest incident with leaked data. It doesn't distinguish itself from siblings like search_breaches or recent_breaches, which is the only reason it falls short of a 5.

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?

Usage is implied by the framing ('services a person uses') and bounded by 'up to 10', so an agent can infer this is a per-service lookup rather than a free-text search. However, there is no explicit guidance on when to pick this over search_breaches or recent_breaches, and no stated prerequisites.

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