Skip to main content
Glama

Explore21 MCP

Search Learn and Guides

search_learn
Read-only

Find Explore21's teaching pages: the course «Биткойн от нулата» (Bitcoin from zero), the guides and the glossary words, in English and Bulgarian. Returns titles, links and a short excerpt; link the page rather than retelling it. Show the closing "Source:" line to the user.

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

Input Schema

NameRequiredDescriptionDefault
langNoWhich language comes first; guessed from the query if left out.
queryYesThe words to search for, in English or Bulgarian.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description goes further by disclosing the return shape (titles, links, a short excerpt) in the absence of an output schema. It also sets a post-retrieval contract — link rather than retell, and surface the closing "Source:" line — which is behavior an agent could not infer from structured fields. It does not cover zero-result behavior or result limits, which keeps it short of a 5.

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?

Three dense sentences, front-loaded with what is searched before moving to what is returned and how to present it. Every clause carries information; only the quoted "Source:" instruction is slightly opaque out of context and could have been phrased more precisely.

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?

A two-parameter read-only search with no output schema needs to describe its returns, and this description does (titles, links, excerpt). Language scope is stated. Missing only edge details such as no-match behavior or result count, which are minor for a tool of this complexity.

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%: the query and lang parameters, including the enum and the "guessed from the query if left out" fallback, are fully documented in the schema. The description's only added signal is that both English and Bulgarian are supported, which corroborates rather than extends the schema. 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?

Uses a specific verb ("Find") and a precisely bounded resource set: course pages, guides, and glossary entries for the named course «Биткойн от нулата», in two named languages. Nothing about it could be confused with the metric-oriented siblings (list_metrics, get_metric), so an agent can select it from the name plus description alone.

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?

Scope of content is implied clearly (teaching pages, guides, glossary), but there is no explicit when-to-use statement, no exclusion, and no named alternative. The two presentation instructions ("link the page rather than retelling it", "Show the closing 'Source:' line") steer how to use results rather than when to call the tool, so guidance is present but only implied at the selection level.

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