Skip to main content
Glama

register_datasource

Idempotent

Register a datasource manifest from a YAML/JSON file or Python module path into the ontology database, making its data sources available for concept resolution and fetching.

Instructions

Register a datasource manifest into the ontology database.

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": {
      "manifest_path": "<manifest_path>"
    },
    "name": "register_datasource"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifest_pathYesPath to YAML/JSON manifest file, or Python module path "pkg.mod:CATALOG"

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=true, openWorld=false), so the description does not need to restate them. It contributes the destination context ('into the ontology database'), but is silent on validation failures, what an idempotent re-registration actually does, and whether existing entities are touched.

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?

One sentence, front-loaded with the action and target, and zero filler. For a single-parameter tool this is an appropriate size; the gaps are in coverage, not in verbosity.

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 no explanation, and annotations cover the safety profile. However, for a write tool that registers into a persistent ontology, the definition never explains side effects on existing data or error conditions, leaving the picture only minimally complete.

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 100% and the single parameter is fully documented in-schema, including the YAML/JSON path form and the 'pkg.mod:CATALOG' module syntax. The description adds nothing beyond the schema, so the baseline of 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 and resource: register a datasource manifest into the ontology database. That is enough to distinguish it from data-inspection or graph-query siblings, but it does not explicitly separate it from nearer alternatives such as register_discovered, import_catalog, or import_crosswalks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no statement of prerequisites, no mention of when to prefer this over register_discovered or import_catalog, and no note about whether re-registering an existing datasource is expected or an error. The agent must infer the choice of tool from the name alone.

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