Skip to main content
Glama

import_crosswalks

Idempotent

Ingests bundled crosswalk YAML files as mappings, enabling concept-to-column resolution and source ranking without manual mapping setup.

Instructions

Ingest the shipped crosswalk registry (crosswalks/*.yaml) as mappings.

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_crosswalks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and repeatability profile is covered. The description adds the source location (crosswalks/*.yaml) and that results become mappings, but says nothing about merge/overwrite behavior toward pre-existing mappings, which is the main remaining behavioral question.

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?

A single short sentence with the source and the effect front-loaded and no filler. Nothing could be removed without losing 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?

For a zero-argument import tool with an output schema and rich annotations, the description covers what is ingested and what it produces, which is enough to call it correctly. The only unaddressed point is how existing mappings are treated on re-import, a minor gap given idempotentHint is already declared.

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?

The tool takes zero parameters and the schema is an empty object with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing.

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 ('Ingest') and a specific resource ('the shipped crosswalk registry (crosswalks/*.yaml)') plus the resulting effect ('as mappings'). It is clear what the tool does, though it does not explicitly distinguish itself from the similarly named sibling import_catalog.

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 word 'shipped' signals this loads the bundled registry rather than user-supplied data, which suggests a seeding/initialization role. There is no explicit when-to-use, when-not-to-use, or named alternative such as import_catalog.

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