Skip to main content
Glama

Find public tools by task

toolfound_find_by_task
Read-onlyIdempotent

Match a plain-language task description against public Toolfound catalogue evidence. Use it when someone asks which tool can do a specific job, such as converting invoices or scheduling social posts, and you want listed candidates rather than a general web search. Returns up to a handful of matching listings with name, tagline, listing URL, pricing model, the terms that matched and any limitations. Results are not personal recommendations and unknown capabilities remain unknown.

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": {
      "task": "<task>"
    },
    "name": "toolfound_find_by_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesThe job to get done, described in everyday words, for example send invoices to clients. Name the outcome, not a product.
pricingNoOptional pricing filter. free keeps only free tools, free_or_freemium also keeps tools with a free tier, any applies no filter. Listings with unknown pricing are excluded when a filter is set.

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
queryYes
matchesYes
warningsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / pricing / description
      Added value: +"Optional pricing filter. free keeps only free tools, free_or_freemium also keeps tools with a free tier, any applies no filter. Listings with unknown pricing are excluded when a filter is set."
    • addedInput schema / properties / task / description
      Added value: +"The job to get done, described in everyday words, for example send invoices to clients. Name the outcome, not a product."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the bar is lower; the description adds genuine context by bounding result volume ('up to a handful'), listing what each result contains, and warning that results are not recommendations and unknown capabilities stay unknown. It does not mention rate limits or authentication, but none appear to apply to a public read tool.

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?

Four sentences, each carrying distinct information: purpose, usage trigger, return shape and an epistemic caveat. The trigger is front-loaded immediately after the purpose statement, with no redundant restatement of the name or title.

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 an output schema present and full parameter coverage, the description only needs to carry the matching intent and interpretive caveats, which it does. It could say slightly more about how matching strength should be read, but nothing essential to a correct call is missing.

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%, with both the task string and the pricing enum fully documented in the schema, including the exclusion of unknown-pricing listings. The description only echoes 'plain-language task description' and adds no syntax or filtering guidance beyond that baseline.

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 ('Match a plain-language task description against public Toolfound catalogue evidence') and contrasts it with a general web search. It stops short of distinguishing itself from the catalogue-search sibling toolfound_search_tools, so an agent must infer that boundary.

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 concrete trigger ('when someone asks which tool can do a specific job') plus two examples and a negative cue ('rather than a general web search'). No explicit when-not or named alternative among the sibling tools is offered.

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