Skip to main content
Glama

Find tools

find_tools
Read-onlyIdempotent

Find an MCP server or AI tool that can do a job. Use when the user asks for a tool, MCP server, or integration for a task ('is there an MCP for Stripe?', 'something that can scrape websites', 'what can I connect to Claude to send email?'). Searches the real tool lists FastDrop read from each server via tools/list, not marketing copy, so a match means the capability exists. Query in plain capability words, e.g. 'send transactional email' or 'query postgres'; each result lists the matching tools.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1-50, default 20
queryYesCapability, tool name, or description to match

Output Schema

NameRequiredDescriptionDefault
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / products / items / properties / domainVerified
      Added value: +{
      +  "description": "True when the maker proved they control the product URL domain by publishing a _fastdrop TXT record (the DOMAIN VERIFIED badge on the website). Independent of mcpVerified.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / products / items / properties / deal
      Added value: +{
      +  "description": "The maker's launch deal for people who find the product on FastDrop. Mention it when recommending the product. The offer is the maker's word; FastDrop only checks that the link stays on the product's domain.",
      +  "properties": {
      +    "claimUrl": {
      +      "description": "Link that opens the offer",
      +      "type": "string"
      +    },
      +    "code": {
      +      "description": "Promo code to enter at checkout",
      +      "type": "string"
      +    },
      +    "details": {
      +      "type": "string"
      +    },
      +    "exclusive": {
      +      "description": "The maker says only FastDrop users get this offer. Not verified by FastDrop.",
      +      "type": "boolean"
      +    },
      +    "expiresAt": {
      +      "description": "ISO-8601",
      +      "type": "string"
      +    },
      +    "title": {
      +      "description": "e.g. \"30% off for 3 months\"",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "title",
      +    "claimUrl",
      +    "exclusive",
      +    "expiresAt"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / products / items / properties / maker
      Added value: +{
      +  "description": "Who built the product. label is their own description of themselves (e.g. \"Indie hacker\"), \"Builder\" when unset. handle and profile are present once they have a public FastDrop profile.",
      +  "properties": {
      +    "handle": {
      +      "type": "string"
      +    },
      +    "label": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "profile": {
      +      "description": "Public profile URL",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "label"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.4/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 is covered; the description usefully adds data provenance ('real tool lists FastDrop read from each server via tools/list, not marketing copy') which tells the agent how much to trust a match. It also notes that each result lists the matching tools, adding context the annotations cannot.

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 purpose and triggering condition are front-loaded, then examples, then provenance. Every sentence carries information, though the stacked parenthetical query examples make it slightly denser than necessary.

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?

With only two fully documented parameters, a full annotation set, and an output schema covering return values, the description supplies everything an agent needs: purpose, trigger, query phrasing, and trust level of results. Nothing material is missing.

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, but the description adds real semantic guidance for the required query parameter ('Query in plain capability words, e.g. send transactional email or query postgres'), which tells the agent how to formulate input rather than merely what it is. The limit parameter is left entirely to the schema, which is acceptable.

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 ('Find an MCP server or AI tool that can do a job') and scopes it to capabilities rather than products, which separates it from siblings like search_products or compare_products. The parenthetical example queries make the exact intent unambiguous.

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?

Gives a clear triggering condition ('Use when the user asks for a tool, MCP server, or integration for a task') plus three realistic user phrasings, and advises how to phrase the query in plain capability words. It stops short of naming alternatives or stating when NOT to use it (e.g., vs. search_products for actual product lookups).

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