Skip to main content
Glama

Find Tool Tool

find_tool
Read-only

Finds the UUTOOLS.NET tools for a task – e.g. "heic to jpg", "compress pdf", "resize image for instagram", "mp4 to mp3" – and returns the best matches with a link to each tool page. Give the user the link: the tool runs on that page, free and without an account.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tools (1–10, default 5).
queryYesThe task in a few words, in any of the site languages, e.g. "heic to jpg" or "pdf komprimieren".
languageNoLanguage of the pages to link: en, es, nl, it, de, hr, bs, sr, fr (default en).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds genuinely new behavioral context: it returns best matches plus a per-tool page link, the tool executes on that page, and it is free with no account required. It stops short of describing match count or fallback behavior when nothing matches, which keeps it at a 4.

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?

Two tight sentences with the core action front-loaded and the examples inline where they are most useful. The trailing instruction about giving the user the link earns its place as agent-facing behavior, and there is no filler.

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 three fully documented parameters and no output schema, the description supplies what an agent still needs: what comes back (best matches with links) and what to do with it (hand the link to the user). Only edge-case behavior, such as no-match results, is unaddressed.

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%, so limit, query, and language are already documented in the input schema. The description reinforces the query semantics with task-phrasing examples but adds no format, ranking, or language-matching 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (finds) and resource (UUTOOLS.NET tools for a task) and gives four concrete query examples ("heic to jpg", "compress pdf", "resize image for instagram", "mp4 to mp3") that pin down the intent. It never explicitly contrasts itself with the sibling list_categories, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the examples: describe the task in a few words and search. The second sentence gives post-call guidance ("Give the user the link") rather than when-to-use-this-vs-alternatives guidance, and there is no exclusion or precondition stated, so guidance stays at an implied level.

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