Skip to main content
Glama

resource_catalog_import

DestructiveIdempotent

Indexes existing potential catalogs or author-project tier JSON without downloading or modifying files, preserving original status, license, file roles, and hashes for reuse.

Instructions

Index an existing potential catalog (record.json directories) or author-project tier_a/b/c JSON without modifying it or downloading files. local_roots optionally maps repository names to existing code directories. Retain original status, license, file roles and hashes. Repeated imports reuse entries; failures remain explicit.

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": "<source>",
      "op_id": "<op_id>"
    },
    "name": "resource_catalog_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
sourceYes
local_rootsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, and the description usefully adds that repeated imports reuse entries, failures stay explicit, and nothing is downloaded. What it omits is the destructive half: it never says what existing index entries or records can be overwritten, and the phrase "without modifying it" is ambiguous enough that an agent could misread the tool as read-only, despite readOnlyHint=false.

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?

Four short, front-loaded sentences with no filler; the core operation and the two modes come first. The density of undefined jargon costs some readability, but nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 not be described, and idempotency behavior is covered. For a destructive, non-read-only tool with a required unexplained parameter, the absence of any note on what gets overwritten, what permissions are needed, or when to prefer a sibling leaves meaningful gaps.

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 coverage is 0%, so the description carries the full burden and partially meets it: "source" is clarified as record.json directories or tier_a/b/c JSON, and local_roots is explained as a repository-name to code-directory mapping. The required op_id parameter is never explained at all, leaving one of three parameters opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb ("Index") and the two accepted resource shapes ("record.json directories" and "author-project tier_a/b/c JSON") are stated, which is more than a bare restatement of the name. However, domain jargon like "potential catalog" and "tier_a/b/c" is undefined, and nothing distinguishes this from the sibling project_import or resource_register, so an agent still has to guess at the boundary.

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 only implied: the two input modes suggest when the tool applies, and "without... downloading files" implies a local-only constraint. There is no explicit when-not guidance, no named alternative for bulk import or registration, 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.