Skip to main content
Glama

Search the Toolfound directory

toolfound_search_tools
Read-onlyIdempotent

Search toolfound.com, the launch platform and tool directory built agent-first, for SaaS products and developer tools by name, tagline, or tag. Returns matching products with taglines, pricing model, vote counts, and canonical listing URLs you can cite or open. Use this when a user asks to find, compare, or discover a tool for a job.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for: a product name, a problem it solves, or a tag, such as 'invoicing' or 'screenshot api'. Matching is keyword based, so specific nouns work better than full sentences.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Free-text search: product name, problem, or tag (e.g. 'invoicing', 'screenshot api')."New value: +"What to look for: a product name, a problem it solves, or a tag, such as 'invoicing' or 'screenshot api'. Matching is keyword based, so specific nouns work better than full sentences."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the bar is lower. The description still adds useful context by naming what comes back (taglines, pricing model, vote counts, canonical listing URLs that can be cited) — valuable since there is no output schema — but says nothing about result caps, ranking, or empty-result behavior.

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?

Three sentences, front-loaded with the resource and capability, then return payload, then usage trigger. The 'launch platform and tool directory built agent-first' clause is positioning copy that does not help an agent decide or call correctly.

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?

For a single-parameter, non-destructive lookup with no output schema, the definition covers what it searches, what it returns, and when to reach for it. Remaining gaps (pagination, result count, ranking) are minor for a search tool at this complexity.

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% and the single 'query' parameter is already documented with examples and a keyword-matching caveat. The description's 'by name, tagline, or tag' largely restates the schema's 'a product name, a problem it solves, or a tag', so it adds little beyond the structured field.

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 toolfound.com ... for SaaS products and developer tools') plus the matchable fields (name, tagline, tag). It stops short of distinguishing itself from close siblings such as toolfound_find_by_task or toolfound_get_product, and its own 'find ... a tool for a job' phrasing overlaps with a task-based finder.

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?

The closing sentence gives a clear trigger: use it when a user asks to find, compare, or discover a tool for a job. There are no exclusions or named alternatives, so an agent facing a task-oriented query has no guidance on whether toolfound_find_by_task is the better route.

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