Skip to main content
Glama
Sign In
tool-disco

tool-disco

by egoughnour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discover_tools

Match a natural language goal to available tools. Get candidate tools and compositions that can accomplish the task.

Instructions

Discover tools that match a natural language goal description. Returns tool candidates and compositions that can accomplish the task.

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": {
      "goal": "<goal>"
    },
    "name": "discover_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesNatural language description of what you want to accomplish
contextNoAdditional context about the task
examplesNoExample inputs or outputs
constraintsNoConstraints or requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the output (tool candidates and compositions) but lacks details on read-only nature, side effects, or return format. This is adequate but not comprehensive.

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 a single, front-loaded sentence that immediately conveys the tool's purpose with no wasted words.

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?

The tool has no output schema and moderate complexity, but the description covers the core behavior and return value. It could be improved by specifying the exact structure of candidates/compositions, but it is sufficient for basic usage.

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 baseline is 3. The description adds no extra parameter-specific meaning beyond the overall goal-focused purpose.

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 clearly states the tool's function: discovering tools based on a natural language goal. It distinguishes itself from siblings like list_candidates and plan_capabilities_for_goal by focusing on goal-driven discovery.

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 description implies the usage context: when you have a natural language goal and need to find tools or compositions. It doesn't explicitly mention alternatives or when not to use it, but the intended scenario is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools