Skip to main content
Glama

Search published resources

search_resources
Read-only

Use this tool when a search needs extra filters: learning language, a verified age range, the published flag, or paging. It lexically searches published North Dakota Fairytales school lessons, books, songs, videos, games, coloring pages, stories, and encyclopedia articles. It does not translate the query and does not rank the brand in outside search engines. For a simple query, find_ndf_content is the shorter call.

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

Input Schema

NameRequiredDescriptionDefault
ageNoMatch only resources with a verified age range that includes this age.
limitNoPage size, from 1 to 20.
queryNoLexical query, maximum 200 characters. Omit it to list by filters.
localeNoInterface locale code from the 77-locale registry, such as en, ru, ar, or zh-Hans.
offsetNoNumber of matches to skip.
categoryNoPublished product category: organization, school, encyclopedia, books, songs, video, games, coloring-pages, or stories.
publishedNofalse returns no rows because the catalog stores published resources only.
learningLanguageNoLanguage being taught, when the resource records one. This is not the interface locale.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With readOnlyHint/openWorldHint=false/destructiveHint=false already covering the safety profile, the description still adds real behavior: matching is lexical rather than translated or semantic, and results are limited to the published catalog. It does not describe result ordering or what a returned record contains, which leaves a gap for a no-output-schema tool.

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?

Three sentences, front-loaded with the selection condition, then scope, then the alternative. Every clause carries routing or behavioral information with no filler.

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?

For an 8-parameter, all-optional search tool with no output schema, the description covers what is searched, which filters differentiate it, and when to pick the sibling instead. It stops short of describing pagination defaults or result shape, which would fully close the loop.

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 each of the 8 parameters is already documented, including the learningLanguage vs. locale distinction and the published=false no-rows behavior. The description adds only the framing that learning language, verified age range, published flag, and paging are the filter set, without new syntax or default values. Baseline 3 is appropriate.

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 ('lexically searches published North Dakota Fairytales school lessons, books, songs, videos, games, coloring pages, stories, and encyclopedia articles') and frames its differentiator as extra filters. It also names the sibling it is not ('For a simple query, find_ndf_content is the shorter call'), so an agent can route without opening either 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?

The opening sentence gives an explicit trigger ('when a search needs extra filters: learning language, a verified age range, the published flag, or paging') and the closing sentence names the alternative for simple queries. It also states two exclusions: no query translation and no ranking of the brand in outside search engines.

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