Skip to main content
Glama

Export context as Apache Ossie

export_ossie
Read-only

Get a connection's context as an Apache Ossie semantic model in YAML: tables and columns with descriptions and synonyms, notes for AI, and definitions as metrics. Use it when the user wants the model as a file, for another tool, or to edit and bring back with import_ossie. For answering questions, use get_context instead. Read-only. Refused on an approved_queries connection.

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>"
    },
    "name": "export_ossie"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionIdYesConnection id from list_connections.

Output Schema

NameRequiredDescriptionDefault
yamlNoThe Ossie model as YAML text.
filenameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so 'Read-only' restates structured data rather than adding to it. The one genuinely new behavioral fact is the refusal on an approved_queries connection, which is valuable; the description says nothing further about size limits or what happens on failure, so with annotations carrying most of the weight this lands at adequate-plus.

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?

Three tight sentences: what it produces, when to use it versus get_context/import_ossie, and the refusal condition. The output format and alternatives are front-loaded and nothing is padded.

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?

An output schema exists, so return values needn't be described, and the description still previews the model's contents (tables, columns, descriptions, synonyms, notes, metrics). Combined with explicit sibling routing and a connection-type restriction, an agent has everything needed to select and call it correctly.

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?

Only one parameter and schema coverage is 100%, with the schema itself pointing to list_connections for the id. The description adds no syntax or format detail about connectionId, so the baseline of 3 applies — the schema does all the work here.

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?

Names a specific verb and resource ('Get a connection's context') plus the exact output artifact ('Apache Ossie semantic model in YAML'), and enumerates its contents. It is immediately distinguishable from siblings get_context and import_ossie.

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?

Gives explicit when-to-use ('wants the model as a file, for another tool, or to edit and bring back with import_ossie') and an explicit when-not with a named alternative ('For answering questions, use get_context instead'). It even adds a precondition-based exclusion ('Refused on an approved_queries connection').

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