Skip to main content
Glama

import_catalog

Idempotent

Import one named fd-* provider registry or all of them into the catalog to register available data sources for later concept resolution and fetching.

Instructions

Import one (by name) or all fd-* provider registries into the catalog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "import_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world operation, so the description need not restate safety. What it fails to disclose is behavior-specific context: where the fd-* registries come from, whether an existing catalog entry is overwritten or merged on re-import, and what side effects occur — critical for a write/import tool.

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?

One sentence, front-loaded with the verb and scope split, with no filler. It is arguably over-terse for a tool with zero schema coverage, but there is no wasted wording to trim.

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 annotations cover the safety profile. Still, for an import operation the description omits the source/destination of the registries, overwrite semantics, and failure modes, leaving real gaps an agent would want before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description had to carry the meaning of the single 'provider' parameter, and it does: passing a name imports one registry, omitting it imports all. The 'fd-*' hint also signals the expected value shape. It stops short of saying whether the name is the exact provider key or a prefix match.

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 and resource ('Import ... provider registries into the catalog') and states the two scope modes (one by name, or all). It is clear what the tool does, but it does not differentiate itself from the adjacent sibling import_crosswalks, which an agent could easily confuse with this one.

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?

The phrase 'one (by name) or all' implicitly tells the agent to omit the provider argument to import everything, which is useful. However, there is no explicit when-to-use guidance, no mention of import_crosswalks as the alternative for crosswalk data, and no prerequisites or ordering advice.

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