Skip to main content
Glama

mureo_consult_advisor

Search external knowledge bases for relevant snippets by submitting a diagnostic question, enriched with campaign context, when internal history is insufficient.

Instructions

Consult external advisor MCP servers (vector search) for fragments relevant to a specific question. mureo enriches the question with the local campaign state (metrics, recent action log, STRATEGY.md) before forwarding it to every server configured in ~/.mureo/insight_sources.json. Each server returns top-k snippets with similarity scores; the agent reasons over them. Use this when /learn history is thin or when you need a second opinion from a shared knowledge base (consulting cos, industry benchmarks, OSS communities, internal wikis).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesThe specific diagnostic question to search for. Concrete > generic — 'why is CPA up 30% on Brand-Search?' beats 'tips for Google Ads'.
campaign_idNoOptional campaign id. When supplied, mureo attaches the campaign's name / status / budget and the last few action-log entries to the query so the advisor's vector search has richer context to match against.
Behavior4/5

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

Discloses enrichment of question with local campaign state, forwarding to multiple servers, and return of top-k snippets with similarity scores. Lacks details on error handling or rate limits but adequate for a consult 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?

Two sentences with clear front-loaded purpose, efficient and no wasted words.

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?

Complete for purpose and usage guidance; lacks details on output format or error scenarios but given no output schema, it is sufficient.

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

Parameters4/5

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

Schema coverage is 100% so baseline 3. Description adds context that campaign_id attaches campaign state, enhancing value beyond schema descriptions.

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 tool consults external advisor MCP servers via vector search for relevant fragments. It distinguishes from sibling tools by focusing on external knowledge base queries, not direct account management.

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?

Explicitly guides when to use: 'when /learn history is thin or when you need a second opinion', and lists example knowledge sources.

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/logly/mureo'

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