Inspect Concept in Local / Uploaded Ontology

Get a full profile of a class or concept from a local or uploaded ontology.

CRITICAL — file access workflow:

1. Try file_path first (works only if the file is readable by the MCP server process).

2. If file_path fails for any reason → call get_upload_instructions with the local path, execute the returned curl command via Bash tool, parse the id from the JSON response, then call this tool again with upload_id.

3. NEVER read the file content and pass it through the conversation. NEVER attempt to parse or analyse the TTL text manually. The upload workflow sends raw bytes directly from disk to server without the AI ever seeing the content — it is always faster, cheaper, and more reliable.

Quale modalita di input usare:

• stdio / stessa macchina → file_path

• server remoto, file grande → get_upload_instructions + upload_id

• server remoto, file piccolo (<1 MB) → valuta content + format con inspect_local_ontology, poi passa a upload se servono query ripetute

Args:

• uri: URI of the class/concept to inspect

• file_path / upload_id: exactly one (see workflow above)

• mode: "raw" | "effective" (default: "effective")

Tip: Use search_concepts first if you are checking whether a similar concept already exists in schema.gov.it. Use this tool only after you know you want to inspect the local/uploaded ontology.

mode: "raw" — only triples explicitly present in the local file:

• definition, hierarchy, usage, own_properties (rdfs:domain asserted directly on this class)

• No ancestor traversal, no incoming/outgoing

mode: "effective" (default) — full OWL/RDFS-implied view:

• All raw sections, plus:

• inherited_properties: properties from superclasses via rdfs:subClassOf+/skos:broader+, each annotated with the ancestor that declares them

• incoming / outgoing: data-level relations via instances

Distinguishing own vs inherited:

• own_properties = rdfs:domain explicitly written as this class in the local file

• inherited_properties = rdfs:domain written on an ancestor class (traversed via property paths)

• Properties applicable only via owl:restriction or anonymous class expressions are NOT shown — use query_local_ontology for those

Limitation with owl:imports: inherited_properties traverses only superclasses present in the local file. Classes from imported external ontologies (e.g. l0:, COV:, CPV:) are absent from the local store unless the file includes them. For complete property semantics of a property that subPropertyOf an external one, use inspect_local_property instead — it falls back to schema.gov.it for missing super-properties.

When to use this vs X:

• vs inspect_concept: use this for a local or uploaded ontology; use inspect_concept for the remote schema.gov.it catalog

• vs query_local_ontology: use this when you want the standard profile of one concept; use query_local_ontology only for custom SPARQL questions not covered here

Unicode SPARQL note: oxigraph rejects prefixed names with non-ASCII local parts (e.g. myont:modalità_cup). Always use full URIs in angle brackets (<https://...#modalità_cup>) for properties or classes with Unicode in the local name.