Skip to main content
Glama
Sign In

nope-mcp — Open Educational Resources search

by org.edufeed
OverviewDiscussionsAdmin

Resolve Publisher/Creator Name to Canonical Metadata Spelling

resolve_publisher
Read-onlyIdempotent

Resolve an actor name (organization or person) to the EXACT spelling used in the AMB metadata, so it can be passed to the publisherName/creatorName filters of search_resources. Those filters are exact full-string matches (case-insensitive), so a guessed spelling like "Lehreladen" silently misses the stored "LEHRE LADEN". This tool free-text searches the name and returns the similar publisher/creator names found in the corpus, with the field they appear in and a resource count. Distinct from resolve_author, which resolves Nostr signing accounts (kind-0 profiles) to pubkeys — metadata publishers usually have no Nostr account at all.

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": {
      "name": "<name>"
    },
    "name": "resolve_publisher"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesActor name as the user said it (e.g. "Lehreladen").
relaysNoRestrict the lookup to specific relays. Only relays returned by list_relays (default or extra) are accepted, by full URL or short name (e.g. "oersi", "sodix"). Default: the default relay set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, but the description adds genuinely new behavior: the lookup is free-text rather than exact, and it returns similar publisher/creator names plus the metadata field they appear in and a resource count. It does not say how many candidates come back or whether results are ranked or truncated, which is the main remaining gap.

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?

Front-loaded with the verb and purpose, then the failure mode, then the sibling distinction — every sentence carries information. The final resolve_author sentence is long and could be tightened, but it is not padding.

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?

For a two-parameter, closed-world read tool with no output schema, the description covers what goes in, what comes back (names, field, resource count), why precision matters, and how it differs from the nearest sibling. 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.

Parameters3/5

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

Schema description coverage is 100% and both parameters (name, relays, including the list_relays provenance constraint and default relay set) are documented there, so the baseline is 3. The description adds only the rationale that the name should be the raw user-supplied spelling, which the schema already says.

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 (resolve an actor name — organization or person — to the exact spelling stored in AMB metadata) and explicitly separates itself from resolve_author by explaining that the sibling resolves Nostr kind-0 profiles while this tool resolves metadata publishers. An agent can pick between the two without opening a schema.

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?

Gives the concrete downstream use case (passing the result to publisherName/creatorName filters of search_resources), the condition that motivates it (those filters are exact full-string, case-insensitive matches, so a guessed spelling like "Lehreladen" silently misses "LEHRE LADEN"), and the alternative path (resolve_author) with the reason it is usually wrong here.

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