Skip to main content
Glama

find_tools

Read-onlyIdempotent

Free, no key. PazAIr has more tools than the list you were given: this finds them. Say what you want to do in a few words (e.g. "refund", "tender", "subscription", "licence", "report of my advertisement") and get the matching tools with their full definitions; call one with use_tool. Leave words out to get every tool by name with one line each.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tools to return in full, 1 to 20. Default 8.
wordsNoWhat you want to do, in a few words, e.g. dispute an order. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered; the description adds what annotations cannot — no key or payment required — plus the two distinct output shapes (full definitions vs. one line per tool). That is exactly the extra behavioral context the structured fields omit.

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?

The core capability and the use_tool handoff are front-loaded in the first two sentences, and the examples of intent words are genuinely useful. The opening "Free, no key" is slightly promotional but carries real auth information, so it largely earns its place.

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?

There is no output schema, so the description must carry the return-shape burden, and it does describe both result formats and the follow-up tool. It stops short of saying how results are ordered or what a "full definition" contains, which is a minor gap for a two-parameter discovery tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns a bump by explaining the semantic effect of the optional 'words' parameter and of leaving it empty — a cross-parameter behavior the schema alone does not convey. It never mentions the 'limit' parameter, though the schema documents it fully.

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?

The description states a specific verb and resource — it finds tools that exist beyond the list the agent was given — and explicitly positions itself against use_tool ("call one with use_tool"). An agent can tell immediately that this is a discovery/search tool rather than an execution or listing tool.

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?

It gives both operating modes with conditions: supply a few words describing an intent to get matching full definitions, or omit words to get every tool name with a one-line summary. It also names the follow-up step (invoke a result via use_tool), so the when/how/when-not chain is complete.

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