Skip to main content
Glama
italia

Schema.gov.it MCP Server

Official
by italia
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Execute SPARQL Query

query_sparql
Read-onlyIdempotent

Execute raw SPARQL queries against the Schema.gov.it catalog for ad-hoc exploration and analysis of Italian government data.

Instructions

Execute a RAW SPARQL query against schema.gov.it.

Args:

  • query: The SPARQL query to execute (prefixes are auto-injected)

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

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

Returns:

  • Compressed JSON result (tabular for >5 rows, object array otherwise)

Examples:

  • SELECT ?s ?p ?o WHERE { ?s ?p ?o } LIMIT 10

  • SELECT ?class (COUNT(?s) AS ?count) WHERE { ?s a ?class } GROUP BY ?class

When to use this vs X:

  • vs query_local_ontology: use this for the default remote catalog schema.gov.it; use query_local_ontology for a file/store loaded locally or via upload_id

  • vs query_external_endpoint: use this for the built-in schema.gov.it endpoint; use query_external_endpoint only for another HTTPS SPARQL endpoint

  • vs specialized tools: use this only when no dedicated tool already covers the task

Do not use this if:

  • you need a concept profile → use inspect_concept

  • you need property semantics → use get_property_details

  • you need to search by keyword without a known URI → use search_concepts

  • you need to browse a vocabulary or dataset → use the dedicated vocabulary/dataset tools

Important: raw hybrid SPARQL is not supported yet. Use source="hybrid" only on specialized concept/property tools, not here.

Note: Use this for ad-hoc exploration. Prefer specialized tools for common operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe SPARQL query to execute
formatNoRDF content type for inline content
sourceNoExecution context: "schema" for schema.gov.it, "local" for a file/uploaded store. "hybrid" is reserved and not supported for raw SPARQL.schema
contentNoInline RDF content when source='local'
file_pathNoAbsolute path to a local ontology file when source='local'
upload_idNoUploaded ontology store ID when source='local'

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Adds behavioral details beyond annotations: prefix auto-injection, compressed JSON response format, unsupported hybrid mode. No contradiction with annotations.

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?

Well-structured with sections (Args, Returns, Examples, guidance), but somewhat lengthy. Every sentence adds value, but could be 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 6 parameters, no output schema, and annotations, the description covers the tool comprehensively with examples, return format, and usage scenarios.

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%, but description adds context for parameters (grouping, default source, hybrid restriction) and includes examples. Could be slightly more detailed for source parameter.

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 executes a RAW SPARQL query against schema.gov.it, and distinguishes from sibling tools by listing alternatives and disclaimers.

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?

Explicitly provides when-to-use and when-not-to-use guidance with specific alternative tools, making selection unambiguous.

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