Skip to main content
Glama

Search Brain (whole documents) — DEFAULT

flypost_search_source_docs
Read-only

The default way to ground content in the user's own material: whole-document Brain search (vector only, ~2s, no AI billing). Returns the matching source documents with REAL source item ids (usable to pin sources on articles) — read them and pull the quotes, stats and anecdotes you need. Optionally include a relevance pre-check for a topic.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
match_countNo
brand_brief_idNo
include_relevanceNoAlso return how much relevant Brain material exists for this query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the read-only/non-destructive profile, and the description adds genuinely useful behavior: ~2s latency, vector-only with no AI billing, and that returned ids are real source item ids usable for pinning. It does not discuss result limits, ranking, or empty-result behavior.

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?

Front-loaded with the default-designation and the core mechanic, then usage instruction, then the optional flag. Slightly promotional wording ('REAL source item ids') but no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does explain returns (matching source documents plus source item ids), which is the key gap covered. However, for a four-parameter search tool with 25% schema coverage, the missing scoping semantics for brand_brief_id and match_count leave an agent guessing.

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 coverage is only 25% (only include_relevance is documented), so the description carries the burden and mostly fails: it restates the optional relevance pre-check but says nothing about match_count's cap/meaning, brand_brief_id's scoping effect, or query syntax. Three of four parameters get no added meaning.

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 specific verb and resource (whole-document Brain search over the user's own source material) and flags itself as the default, contrasting with an implicit alternative via 'vector only ... no AI billing'. It stops short of naming the sibling it differs from (flypost_search_brain), so the differentiation is inferential rather than explicit.

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 default way to ground content in the user's own material' gives clear when-to-use framing, and 'read them and pull the quotes, stats and anecdotes you need' tells the agent what to do after calling. There is no explicit when-not or named-alternative guidance.

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.