Skip to main content
Glama
Sign In

nope-mcp — Open Educational Resources search

by org.edufeed
OverviewDiscussionsAdmin

Search SKOS Concepts

skos_search
Read-onlyIdempotent

Search for concepts in a SKOS vocabulary. By default searches prefLabel, altLabel, hiddenLabel, and definition.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vocabularyUri": "<vocabularyUri>",
      "query": "<query>"
    },
    "name": "skos_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default: 20, max: 100)
queryYesSearch query
fieldsNoFields to search in. Default: ["prefLabel", "altLabel", "hiddenLabel", "definition"]
languageNoLimit search to this language (e.g., "de"). If not specified, searches all languages.
vocabularyUriYesURI of the vocabulary to search (e.g., "https://w3id.org/kim/hochschulfaechersystematik/scheme")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered structurally. The description adds one genuinely behavioral detail — the default field set searched — but says nothing about result ordering, matching semantics (substring vs. exact), or why results might be empty.

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?

Two tight, front-loaded sentences with no filler; the purpose comes first and the default scope second. The second sentence is mildly redundant with the schema's 'fields' parameter description, keeping it just short of a 5.

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

Completeness3/5

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

With no output schema, the description carries the burden of telling the agent what comes back, and it does not — no indication of result shape, ordering, or how limit interacts with total matches. It is adequate for invocation (required params are clear from the schema) but incomplete for interpreting results.

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 description coverage is 100%, so all five parameters including the default field list and language behavior are already documented in the schema. The description's sentence about default fields largely repeats what the 'fields' parameter description already states, adding no new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Search for concepts in a SKOS vocabulary'), which is unambiguous about what the tool does. It does not explicitly distinguish itself from near siblings like skos_get_concept or skos_get_vocabulary, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the entry point for discovering concepts before fetching a specific one, but the description never says when to use it versus skos_get_concept or the generic search_* tools. No exclusions or prerequisites (e.g., needing a vocabulary URI first) are stated.

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

All nope-mcp — Open Educational Resources search toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources