Skip to main content
Glama

Import Apache Ossie model

import_ossie
DestructiveIdempotent

Bring an Apache Ossie semantic model (YAML, core spec 0.3.0.dev0 or the older semantic_model list) into a connection's context: model description and ai_context become the description and notes for AI, dataset and field descriptions become table and column descriptions, synonyms and labels are added, and metrics become definitions. Nothing the file leaves out is changed or removed, and relationships are not stored. First call it without apply to get a preview of what would change and which datasets and fields match nothing, show that to the user, and call again with apply: true only after they confirm. Changes what every AI tool and person on this connection reads, and is recorded in SaturnSQL with your name. Only make it when the user asked for it or confirmed it. Needs the write scope, the connection's owner or an admin, and a plan that includes Context.

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": {
      "connectionId": "<connectionId>",
      "yaml": "<yaml>"
    },
    "name": "import_ossie"
  }
}

Input Schema

NameRequiredDescriptionDefault
yamlYesThe whole Ossie YAML file as text.
applyNotrue saves the import. Omit or false for a preview that saves nothing.
connectionIdYesConnection id from list_connections.

Output Schema

NameRequiredDescriptionDefault
modelNo
notesNoParts of the file that were left out or shortened.
appliedNoTrue when the import was saved.
summaryNo
unmatchedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, but the description adds material context beyond them: fields omitted from the file are untouched, relationships are not stored, the change is recorded in SaturnSQL under the caller's name, and it requires write scope plus connection owner/admin and a plan including Context. That is exactly the kind of side-effect, authorization, and audit information an agent needs before a destructive write.

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?

It is a single dense paragraph with no filler sentences, and the highest-stakes facts (preview-then-apply, user confirmation) are placed before the authorization details. The run-on structure makes some of the mapping and prerequisite details harder to scan than a short bulleted layout would.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive 3-parameter import with an output schema, everything an agent must know is present: input format and supported spec versions, what is and is not mutated, required scope and permissions, plan prerequisite, and the mandatory two-step confirmation flow. Return-value detail is correctly left to the output schema.

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 100%, so the baseline is 3, but the description adds real meaning: apply is framed as preview-versus-save with a confirmation gate, and yaml is scoped to the whole file including supported spec versions (0.3.0.dev0 or the older semantic_model list). It does not restate parameter syntax, which the schema already covers.

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

Purpose5/5

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

The description opens with a specific verb and resource ('Bring an Apache Ossie semantic model ... into a connection's context') and immediately enumerates the concrete mappings (model description/ai_context to description/notes, dataset and field descriptions to table and column descriptions, synonyms/labels, metrics to definitions). That level of detail lets an agent distinguish it from export_ossie and from generic description setters like set_descriptions.

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

Usage Guidelines5/5

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

It prescribes a full workflow: call without apply for a preview, show that preview to the user, then call again with apply: true only after confirmation. It also states the gating condition explicitly ('Only make it when the user asked for it or confirmed it'), leaving nothing about when to invoke 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