Skip to main content
Glama
santismm

santismm-knowledge

Official
by santismm
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Search Harness Engineering & Agentic AI

search
Read-onlyIdempotent

Run a ranked keyword query across all knowledge content in any language, ignoring accents. Results include relevance scores and matched fields; use before get_* tools for questions, not identifiers.

Instructions

Ranked keyword search across the whole corpus (knowledge, patterns, architectures, governance and the handbook). Matches every language and ignores accents, so query in the user's own words. Each hit carries a relevance score and the fields it matched; follow up with the matching get_* tool for full detail. Use this before any get_* tool whenever you have a question rather than an identifier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 20).
queryYesKeyword or phrase to search for, in any of en/es/pt.
localeNoLanguage of the returned body. Default: en.
domainsNoRestrict to these domains. Omit to search everything, including the handbook.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.4.1
    • addedInput schema / properties / query / maxLength
      Added value: +512
    • addedInput schema / properties / query / minLength
      Added value: +1
    • addedOutput schema / properties / results / items / properties / resource_uri
      Added value: +{
+  "description": "Read this card as an MCP Resource.",
+  "type": "string"
+}
  2. First observedv0.2.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint; the description adds valuable behavioral context: language-insensitive matching, accent ignoring, relevance scores, and matched fields per hit. No contradictions with annotations.

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 tightly worded sentences with the core action first, followed by language behavior, hit contents, and usage guidance. No filler or redundant restatement.

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?

Covers what is searched, how to phrase queries, what results contain, and how to follow up. The only gap is not addressing the relationship to the sibling 'search_all', which could slightly confuse tool selection.

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 coverage is 100%, so parameters are well documented. The description adds some query-level nuance ('Matches every language and ignores accents') but does not enrich limit, locale, or domains beyond the schema.

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?

States a clear verb and resource: 'Ranked keyword search across the whole corpus' with explicit domain coverage. It distinguishes itself from get_* tools but does not differentiate from the sibling 'search_all', which also implies whole-corpus search.

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?

Explicitly instructs when to use: 'Use this before any `get_*` tool whenever you have a question rather than an identifier.' However, it does not mention when not to use it or alternatives like search_all or search_articles.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/santismm/santismm-knowledge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server