Skip to main content
Glama
Sign In
Schema.gov.it MCP Server

Schema.gov.it MCP Server

Official
by italia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Recommend External SPARQL Endpoints

recommend_external_endpoints
Read-onlyIdempotent

Get curated recommendations for public SPARQL endpoints, filtered by category, to pair with schema.gov.it for enriched data queries.

Instructions

Return a curated list of useful public SPARQL endpoints to pair with schema.gov.it.

Args:

  • category: (optional) Filter by endpoint family: "italian-pa", "eu", or "knowledge-graph"

  • limit: Maximum results (default: 10)

Returns:

  • Curated endpoint recommendations with rationale, suggested use cases, and example query ideas

Use when: You want a high-signal shortlist of external endpoints before using query_external_endpoint or explore_external_endpoint.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recommend_external_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of endpoints to return
categoryNoOptional category filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by specifying that results include rationale, suggested use cases, and example query ideas, and that the list is curated (high-signal). No contradictions.

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?

The description is concise and well-structured: a one-sentence purpose, bullet-pointed Args and Returns, and a clear 'Use when' section. Every sentence adds necessary information with no redundancy.

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

Completeness4/5

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

Given no output schema, the description adequately describes the return as curated recommendations with rationale, use cases, and example queries. It also sets context for when to use the tool. Could mention behavior without category filter, but still complete enough.

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?

Schema coverage is 100%, so baseline is 3. The description repeats the parameter names and default but adds little beyond the schema descriptions. Category filter is described as 'endpoint family' with enumerated values, but this is already in 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 the tool returns a curated list of useful public SPARQL endpoints to pair with schema.gov.it, which is a specific verb+resource. It distinguishes from sibling tools by explicitly mentioning use before query_external_endpoint or explore_external_endpoint.

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?

Description includes 'Use when: You want a high-signal shortlist of external endpoints before using query_external_endpoint or explore_external_endpoint', providing explicit context and alternatives. This tells the agent when to use this tool and what to do next.

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

Deploy Server

Other Tools