Skip to main content
Glama
BlueNacho
by BlueNacho

search_mark_knowledge

Search Mark's knowledge base for insights on ecommerce, Facebook Ads, creatives, scaling, and metrics analysis.

Instructions

Busca en la base de conocimiento de Mark Builds Brands. Úsalo para encontrar qué dice Mark sobre cualquier tema de ecommerce, Facebook Ads, creatividades, escalado, análisis de métricas, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
n_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries the full burden. It implies a read-only search operation but does not explicitly state non-destructiveness or any side effects. This is adequate but minimal.

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?

The description is two sentences, front-loading the verb and resource, with no wasted words. It is efficient and directly usable.

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 simple search tool with an output schema (though not shown), the description is mostly complete. It could mention the return format or that results are text excerpts, but the current version is sufficient.

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%, so the description must compensate, but it does not explain the 'query' or 'n_results' parameters. While the purpose is inferable, the lack of any parameter details weakens utility.

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?

The description clearly states the verb 'search' and the resource 'knowledge base of Mark Builds Brands', with specific examples of topics (ecommerce, Facebook Ads, etc.), making the purpose unambiguous.

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?

The description explicitly advises to use it for finding Mark's insights on various topics, which provides clear usage context. No exclusions or alternatives are needed due to lack of siblings.

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/BlueNacho/mark-coach-mcp'

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