fynk MCP

Search automations

search-automations

Read-onlyIdempotent

Search the account's automations by name.

Use this tool when:

You need an automation's UUID to filter list-documents by automation
You want to find automations matching a search term

Returns automations whose name matches the query, most recently created first. Results are capped, so narrow the query if you don't find what you're looking for.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of automations to return (default and max: 25)
`query`	Yes	Search term matched against automation names (case-insensitive, min 3 characters)

Output Schema

Name	Required	Description	Default
`automations`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety behavior is covered. The description adds value beyond that by disclosing result ordering ('most recently created first') and the existence of a result cap with remediation advice, which are traits no annotation conveys.

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?

Purpose is front-loaded in one sentence, followed by a scannable bulleted 'when to use' block and a closing note on ordering and caps. There is no filler, though the bullets could be tightened into a single sentence without losing information.

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?

For a two-parameter read-only search with an output schema present and full schema coverage, the description supplies everything an agent needs: purpose, trigger conditions, matching semantics, ordering, and the cap. Return-value details are rightly delegated to the output schema.

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%, with both 'query' (case-insensitive, min 3 chars) and 'limit' (default and max 25) fully documented in the schema. The description only reinforces the cap concept and adds no syntax or semantics the schema lacks, so it sits at the baseline.

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 account's automations') plus the matching dimension ('by name'). No sibling tool in the list touches automations, so an agent can distinguish this from list-documents, list-templates, and search-imports without opening a 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?

An explicit 'Use this tool when' block gives two concrete triggering scenarios, one of which names the downstream consumer ('You need an automation's UUID to filter list-documents by automation'). That is real routing guidance, though it stops short of stating when not to use it or what to try if results are insufficient beyond 'narrow the query'.

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

All fynk MCP tools Inspect

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

Need Help?