Skip to main content
Glama
italia

Schema.gov.it MCP Server

Official
by italia
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get Property Details

get_property_details
Read-onlyIdempotent

Retrieve detailed property information from schema.gov.it including asserted and inherited domain/range, and redundancy analysis for semantic optimization.

Instructions

Get comprehensive details of a specific property from schema.gov.it, with explicit raw vs effective views.

Args:

  • propertyUri: URI of the property

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

  • source: "schema" | "local" | "hybrid" (default: "schema")

  • file_path / content / upload_id: local context when source="local" or source="hybrid"

Tip: Use search_concepts first if you do not know the URI.

mode: "raw" — only explicitly asserted triples:

  • definition: type, label, comment, rdfs:domain, rdfs:range, rdfs:subPropertyOf, owl:inverseOf, functional flags

mode: "effective" (default) — full inherited view, adds:

  • assertedDomain: rdfs:domain declared directly on this property

  • assertedRange: rdfs:range declared directly on this property

  • superproperties: ancestor chain via rdfs:subPropertyOf+, each with hasDomainLocally / hasRangeLocally flags

  • inheritedDomain: domain values from super-properties, each annotated with ancestor URI and label

  • inheritedRange: range values from super-properties, each annotated with ancestor URI and label

  • effectiveDomain: deduplicated union of assertedDomain + inheritedDomain

  • effectiveRange: deduplicated union of assertedRange + inheritedRange

  • redundancy_analysis: diagnostic view of each asserted value:

    • "redundant": identical to an inherited value — the axiom can be dropped without semantic loss

    • "specialization": a rdfs:subClassOf of an inherited value — genuinely narrows the domain/range

    • "new": not present in any inherited value — adds information not implied by the super-property chain

    • summary counts per category for quick overview

Interpreting the output:

  • If assertedDomain is empty but effectiveDomain is not → domain is inherited; no need to re-assert it on this property

  • If assertedDomain equals effectiveDomain → the domain is fully explicit, not relying on inheritance

  • Use redundancy_analysis.summary to immediately see if the local TTL has redundant axioms or genuine specializations

  • owl:equivalentProperty and owl:equivalentClass expansions are not included (use query_sparql for those)

Hybrid mode:

  • source="hybrid" uses the local/uploaded ontology as the base graph

  • it enriches missing super-property semantics from schema.gov.it when a super-property URI is known locally but absent from the local store

  • it still does not build a generic unified graph or guarantee full owl:imports resolution

When to use this vs X:

  • vs inspect_local_property: use this for a property already published in schema.gov.it; use inspect_local_property for a local/uploaded ontology

  • vs query_sparql: use this for the standard semantic profile of one property; use query_sparql only for custom questions not covered here

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo"raw": only asserted triples. "effective" (default): adds assertedDomain/Range, super-property chain, inheritedDomain/Range, effectiveDomain/Range.effective
formatNoRDF content type for inline content
sourceNoExecution context: "schema" for schema.gov.it, "local" for a local/uploaded ontology, "hybrid" for local base + schema.gov.it enrichment.schema
contentNoInline RDF content when source='local' or 'hybrid'
file_pathNoAbsolute path to a local ontology file when source='local' or 'hybrid'
upload_idNoUploaded ontology store ID when source='local' or 'hybrid'
propertyUriYesURI of the property to inspect

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds extensive behavioral context: mode differences, inheritance details, redundancy analysis, hybrid mode behavior, and what is not included (owl:equivalentProperty expansions).

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?

The description is lengthy but well-structured with clear sections (Args, Tip, mode details, interpretation, hybrid mode, when to use). It front-loads core information and each section earns its place, though could be slightly more concise.

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?

Given the tool's complexity (7 parameters, no output schema), the description is remarkably complete. It explains output interpretation, redundancy analysis, hybrid mode behavior, and limitations, leaving little ambiguity for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage. The description enriches each parameter with detailed explanations of enum values (e.g., mode 'raw' vs 'effective', source 'schema' vs 'local' vs 'hybrid') and the local context parameters, adding significant meaning beyond the schema.

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 clearly states it retrieves comprehensive details of a specific property from schema.gov.it, with explicit raw vs effective views. It also distinguishes itself from sibling tools like inspect_local_property and query_sparql in the 'When to use this vs X' section.

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?

Includes a tip to use search_concepts first if the URI is unknown, and explicitly contrasts with inspect_local_property and query_sparql, providing clear when-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/italia/dati-semantic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server