Skip to main content
Glama
Sign In
sota-agw-mcp

sota-agw-mcp

by thanhtrung665
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Tìm trong thư mục tri thức

knowledge_search
Read-only

Search price lists, catalogues, policies, and contracts in a local knowledge folder using accent-insensitive BM25; returns top matching documents.

Instructions

Tìm (BM25, không phân biệt dấu) trong /knowledge: bảng giá, catalogue, chính sách, hợp đồng…

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

Input Schema

NameRequiredDescriptionDefault
kNo
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuine context beyond that by disclosing the ranking method (BM25) and diacritic-insensitive matching, plus the hard boundary of searching only under <workdir>/knowledge. It still says nothing about result ordering, pagination, or behavior on an empty index.

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?

A single tight sentence with the mechanism, scope, and examples front-loaded and no filler. It is efficient to the point of being terse, leaving the one parameter that controls output size unmentioned.

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 a two-parameter read-only search with an output schema already documenting return values, the description covers location, mechanism, and matching semantics well. The only material gap is the meaning of k, which an agent must guess or take from the default.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description carries the full burden and largely drops it: it never explains that k caps the number of returned results (default 5) or what form the query string should take. Only the matching behavior of the query is hinted at via 'không phân biệt dấu'.

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?

Names a specific action (Tìm/BM25 search), a precise resource and location (<workdir>/knowledge), and enumerates the content types it indexes (price lists, catalogues, policies, contracts). That makes the scope unmistakable, but it never contrasts itself with the closest sibling, file_read, which also reads local content.

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?

Usage is only implied: an agent can infer this is the tool for locating knowledge-base documents by content rather than by path. There is no explicit when-to-use or when-not-to-use guidance, and no mention of choosing file_read for known paths versus this tool for discovery.

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

Deploy Server

Other Tools