Skip to main content
Glama

Find published NDF content

find_ndf_content
Read-only

Use this tool when searching for officially published North Dakota Fairytales educational resources, language-learning lessons, children's books, winter songs, games, coloring pages, or encyclopedia articles. One call searches the published catalog and returns compact results with canonical URLs. Query is required. Locale is optional and defaults to en. Matching is lexical and does not translate the query. An empty result means nothing published matched.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, from 1 to 20.
queryYesWords to match against published titles and descriptions. Required. Maximum 200 characters.
localeNoInterface locale. Defaults to en when omitted.
offsetNoNumber of matches to skip.
categoryNoPublished product category: organization, school, encyclopedia, books, songs, video, games, coloring-pages, or stories.

Output Schema

NameRequiredDescriptionDefault
noteYes
limitYes
queryYes
totalYes
localeYes
offsetYes
searchYes
resultsYes
default_localeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/destructive=false, and the description adds real behavioral context on top: results are compact with canonical URLs, matching is lexical and untranslated, and an empty response means nothing is published rather than an error. It does not mention pagination behavior or result caps beyond what the schema states.

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?

Four tight sentences, front-loaded with the use case, then constraints, then default, then result semantics. Nothing is padded and every sentence carries decision-relevant information.

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 five-parameter read-only search tool with full schema descriptions and an output schema, the description covers the remaining gaps an agent needs: when to reach for it, how query matching works, locale default, and what an empty result signifies.

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%, so baseline is 3; the description earns a notch by explaining that matching is lexical and that the query is not translated, which governs how the required query string is interpreted. The locale and required-query notes largely restate schema content but reinforce the defaults.

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 — searching the officially published North Dakota Fairytales catalog — and enumerates the content types (lessons, books, songs, games, coloring pages, encyclopedia articles). This scopes it clearly against siblings like search_resources, get_resource, or list_products, which target different resource populations.

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?

Opens with an explicit when-to-use trigger ('Use this tool when searching for officially published ... resources') and clarifies the empty-result case. It does not name an alternative or state when-not to use it, so an agent must infer the boundary against search_resources on its own.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources