Skip to main content
Glama

Check the files you have installed

check_installed
Read-onlyIdempotent

Hand over the sha256 of each agent markdown file your project has installed (up to 50; sha256sum .claude/skills/*/SKILL.md gives them, mdr.lock already holds them) and get back, for each one: which public file and version those exact bytes are, how many newer versions exist, and the grade then and now. Bytes that match no version anyone published are said so plainly: a local edit, or a copy from somewhere this registry has not seen.

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": {
      "files": "<files>"
    },
    "name": "check_installed"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish the safe read-only, idempotent, closed-world profile, so the description's added value is in describing the response: per-hash identification of public file and version, count of newer versions, and grade before and after. It also discloses the edge-case behavior for unrecognized bytes (reported as a local edit or an unpublished copy), which is precisely the kind of outcome an agent needs to interpret results.

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 sentences, front-loaded with the action before the payoff, and the parenthetical hash-derivation hint is genuinely useful rather than padding. The first sentence is long and clause-heavy, which slightly hurts scanability, but no sentence is wasted.

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 must explain return values, and it does so with enough specificity (matched file/version, newer-version count, grade delta, explicit miss reporting) to act on results. Together with annotations that cover safety and idempotency, the definition is nearly self-sufficient; only the nested ref/path fields are left to the schema.

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 schema description coverage reported at 0%, the description carries the burden of explaining the input, and it does explain that the values are sha256 digests of installed markdown files and how to produce them. However, it never addresses the nested per-item fields (ref for disambiguating identical bytes, path for echo-back matching) or the exact digest format, so coverage of the schema surface remains partial; the 50-item cap merely restates maxItems.

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 names a concrete verb and resource: it takes sha256 hashes of locally installed agent markdown files and returns the matching published file, version, newer-version count, and grade history. That is far more specific than the title or name alone. It does not explicitly contrast itself with siblings like find_files or file_history, though the hash-to-registry-version framing is distinctive enough that confusion is unlikely.

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?

It gives practical operating context: which files to submit, the batch ceiling of 50, and two concrete ways to obtain the hashes (sha256sum on .claude/skills/*/SKILL.md, or reading mdr.lock). It does not state when not to use the tool or name an alternative for adjacent tasks such as tracing a file's history, leaving that to inference.

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