Skip to main content
Glama
Sign In

Flood Design System

by io.github.tillwithered
OverviewDiscussionsAdmin

Search Flood

search_flood
Read-onlyIdempotent

Find public Flood components, ready-to-use compositions, tokens and agent guidance by name or by describing the UI task in English or Russian. Pass a result ID to read_flood for the full contract.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_flood"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
groupNo
limitNo
cursorNoPass nextCursor with the same search and filters.
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, non-open-world operation. The description adds useful scoping context, namely that it searches public resources and supports natural-language task descriptions in English or Russian, but it does not disclose result pagination, sorting, or the structure of returned search results.

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 definition is two tight sentences with no filler. The core purpose is front-loaded and the follow-up read_flood handoff is placed where it is immediately useful.

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?

The search-to-read workflow is conveyed, which is the most important agent behavior for this tool. However, with five parameters, low schema description coverage, and no output schema, the description does not explain filtering by kind/group, result limits, pagination via cursor, or what the returned list contains.

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 only 20%, so the description should carry more parameter meaning than it does. It clarifies that the search input can be a name or an English/Russian UI task description, but it does not explain kind, group, limit, or cursor semantics beyond what the schema minimally states.

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 uses a specific verb and resource: find public Flood components, compositions, tokens, and agent guidance by name or UI task description. It clearly distinguishes this discovery/search tool from read_flood by saying a result ID should be passed to read_flood for the full contract.

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?

It establishes a clear search-then-read workflow by directing the agent to pass a result ID to read_flood. It does not explicitly state when not to use this tool or compare against flood_info, so it falls short of full alternative guidance.

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

All Flood Design System toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources