Skip to main content
Glama
Flux MCP

Flux MCP

Official
by Flux-Search

search

Read-only

Find ranked web results and read pages to return passages answering a query, with people, places, organizations and dates resolved; unread pages list why.

Instructions

Search the web and get ranked results. Pages Flux reads come back with the passages that answer the query, with people, places, organisations and dates written in. Results it could not read are listed with the reason. Use it to find sources; use lineage to read a specific document or link you already have.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to search for.
enrichNoHow many results to read for passages, up to max_results (default: all). 0 returns results without reading any pages, which is fastest.
max_resultsNoMost results to return (default 10). Out-of-range values are moved inside.
allowed_domainsNoOnly return pages from these sites (up to 10).
blocked_domainsNoNever return pages from these sites (up to 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world profile, but the description adds genuinely non-obvious behavior: pages are actively read, unreadable results are returned with an explicit reason rather than silently dropped, and extracted entities are annotated in the passages. No cost, rate-limit, or freshness caveats are mentioned, which keeps it from a 5.

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?

Four short sentences, front-loaded with the core action, and every sentence carries information about output shape or tool selection. The entity list phrase ("with people, places, organisations and dates written in") is slightly padded but still earns its place by describing the markup returned.

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?

With no output schema, the description carries the burden of explaining returns and does so adequately: ranked results, per-result passages, entity annotations, and an explicit failure channel. Pagination and the exact result envelope are unstated, but for a five-parameter search tool this is close to complete.

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 all five parameters including enrich, max_results and the domain filters are already documented precisely in the schema. The description only obliquely touches the enrich behavior via "Pages Flux reads" and adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ("Search the web and get ranked results") and goes further to describe what comes back: passages, marked-up people/places/organisations/dates, and failures with reasons. The final sentence explicitly separates it from lineage, so an agent can tell the two apart without opening either schema.

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?

"Use it to find sources; use lineage to read a specific document or link you already have" gives a clear use case plus a named alternative with the condition that selects it. It stops short of saying when not to search or how to choose between the unread/results-only modes and the fetch sibling, so it is strong but not exhaustive.

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