Skip to main content
Glama

magne.tools

Find tools for a task

find_tools_for_task
Read-only

The published tools for one task, by name: id, name, kind, tagline, pricing and tool page URL. An unknown task returns an error naming the closest tasks.

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

Input Schema

NameRequiredDescriptionDefault
taskYesA task name or slug from list_tasks, e.g. "send email" or "send-email".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-open-world operation. The description adds useful behavioral detail by listing the returned fields and disclosing that an unknown task returns an error naming the closest tasks, which goes beyond the annotations.

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?

The description is two tightly written sentences with no unnecessary wording. The primary purpose and returned fields are front-loaded, followed by the important error behavior.

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?

For a single-parameter, read-only lookup with full schema coverage and safety annotations, the definition is complete enough to invoke correctly. It states what the tool returns and what happens when the task is unknown, so no output schema is needed.

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%, so the task parameter is already fully documented with name/slug examples and its source from list_tasks. The description reinforces the one-task scope but adds no additional syntax, format, or semantic detail beyond the schema 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?

The description states a specific operation: return published tools for one task by task name. It clearly identifies the result fields (id, name, kind, tagline, pricing, tool page URL), though it does not explicitly distinguish this tool from siblings such as search_tools or get_tool.

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 implied by the one-task lookup and by the schema note that the task comes from list_tasks. However, the description does not explicitly say when to use this tool instead of search_tools or get_tool, nor does it state clear exclusions.

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