Skip to main content
Glama

Fileion

Search tools

search_tools
Read-onlyIdempotent

Search the free online tools on Fileion (PDF, image, text and other tools) by name or short description. Returns up to 10 tools per page with their category and Fileion page address.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1.
queryYesPart of the tool name or description, e.g. "merge pdf".
categoryNoTool category slug, e.g. "pdf".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description does add genuinely new behavioral detail — a 10-result page cap and the fact that category and page address come back — but says nothing about empty-result behavior or relevance ordering. With annotations carrying much of the load, a 3 is fair.

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?

Two tight sentences: the searchable scope and match basis come first, the return shape second. Nothing is repeated and no sentence is 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 no output schema, the description usefully discloses page size and the fields returned, and the input schema fully covers the three parameters. It stops short of describing result ordering or what happens when nothing matches, which would complete the picture for a search tool.

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%, with all three parameters documented including examples ("merge pdf", "pdf" slug). The description only restates that matching is by name or description, adding no syntax, matching rules, or pagination semantics 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?

The description gives a specific verb and resource ("Search the free online tools on Fileion") plus the matching basis (name or short description). It does not, however, distinguish itself from siblings like search_software or search_articles, leaving an agent to infer whether "tools" and "software" overlap.

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 only implied: the phrase "by name or short description" hints at how to drive the search, but there is no explicit when-to-use, when-not-to-use, or named alternative among the sibling search tools. The agent must infer the boundary itself.

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