fynk MCP

Search imports

search-imports

Read-onlyIdempotent

Search the account's imports by name.

Use this tool when:

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

Returns imports 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-imports"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`imports`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.9/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, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: result ordering (most recently created first) and the fact that results are capped with no pagination, plus advice to narrow the query. It doesn't say what to do when zero results are returned, but the gaps are minor.

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 a one-line purpose, then scannable bullets, then a short caveat sentence. The only slight redundancy is restating 'search term'/'matching a search term' which the schema already says.

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 an output schema, full annotations, and complete parameter documentation, the description only needs to supply purpose, ordering, and truncation behavior – all present. An agent has everything required to call it correctly; only edge-case behavior (empty results, case handling) is left to the 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 coverage is 100% – both query and limit are fully documented including the min-length and the max of 25. The description adds only marginal meaning on top, mainly the implication that the cap means results may be truncated and the query should be narrowed. Baseline 3 is appropriate when the schema carries the load.

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: search the account's imports by name. It's immediately clear this is a name-based lookup over imports rather than a general list, but no sibling import tool exists to contrast against, so the differentiation work is deferred to the usage bullets.

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?

Explicit 'Use this tool when' bullets cover both the primary motive (getting an import UUID to feed list-documents) and the secondary case (finding imports by term). It names the downstream tool rather than an alternative competitor, and no when-not guidance or exclusion is given.

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?