Skip to main content
Glama

Search flayr tools

search_tools
Read-onlyIdempotent

[read-only] Finds flayr tools that are not in this list (ads, studio, campaigns, stores, …). Returns name, one-line purpose and toolset. Then call the tool by name, or load its toolset with enable_toolset to get its full schema.

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_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults to return (1-25), e.g. 10. Default 10.
queryNoWords describing the task, e.g. "boost a post" or "posting queue".
toolsetNoOnly search this toolset, e.g. "ads". One of: core, publishing, campaigns, analytics, studio, ads, stores, ops.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing the return shape (name, one-line purpose, toolset) and the follow-on action, though it says nothing about result limits or behavior when nothing matches.

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?

Three short sentences, front-loaded with the scope constraint, then the return shape, then the next step. No filler and no restatement of the title.

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

Completeness5/5

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

No output schema exists, and the description compensates by describing exactly what comes back and how to act on it. For a three-optional-parameter, fully documented search tool, nothing an agent needs is missing.

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 description coverage is 100% — query, limit and the toolset enum are each documented with examples and ranges in the schema itself. The description adds no parameter-level detail beyond the schema, so the baseline 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 ("Finds flayr tools") with an explicit scope restriction: tools that are NOT already in the current list. That scope clause alone distinguishes it from siblings like describe_tool, call_tool and enable_toolset, so an agent can pick it without inspecting other schemas.

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?

Gives the trigger condition (the needed tool isn't in the list) and then names the two follow-on alternatives: call the tool by name directly, or load the toolset via enable_toolset for the full schema. This is a complete when/when-next routing instruction rather than passive context.

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.

Resources