Skip to main content
Glama

Get the AOP-Wiki RDF schema

get_schema_card
Read-only

Retrieve the live AOP-Wiki RDF schema card to learn named graphs, classes, predicates, pitfalls, and prefixes before writing SPARQL queries.

Instructions

Return the AOP-Wiki RDF schema card: the named graphs and what each holds, the classes with instance counts, every predicate used on the main classes with usage counts and an example value, the known pitfalls of this dataset, and the prefixes. Call this once before writing your first SPARQL query in a conversation. Built from the live endpoint, so its counts are current.

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": "get_schema_card"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the card is "built from the live endpoint, so its counts are current," which tells the agent the counts are volatile rather than static documentation. It does not discuss response size, latency, or caching, so the credit is moderate.

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?

Front-loads the verb and resource, then lists contents in a single compact enumeration, followed by two short sentences covering timing and freshness. No filler, and the most decision-relevant fact (call this before querying) arrives early.

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?

A zero-parameter, read-only introspection tool with an output schema present, so the description needn't explain return structure. It still covers what matters: what the card contains, that it is derived from the live endpoint, and when to fetch it. Nothing an agent needs in order to call it correctly is missing.

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?

Takes zero parameters, so per the rubric the baseline is 4. The description correctly implies no inputs are needed by framing the tool as a fixed card fetch, and the schema leaves no ambiguity.

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?

States a specific verb and resource ("Return the AOP-Wiki RDF schema card") and then enumerates exactly what the card holds: named graphs, classes with instance counts, predicates with usage counts and example values, pitfalls, and prefixes. That level of specificity makes it unmistakable against query-oriented siblings like run_sparql or search_examples, even without naming them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit, actionable timing guidance: "Call this once before writing your first SPARQL query in a conversation," and the word "once" signals that repeated calls are unnecessary. It stops short of naming run_sparql or other siblings as the follow-on step, so the routing is implied rather than spelled out.

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