tool-disco
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_toolsA | Discover tools that match a natural language goal description. Returns tool candidates and compositions that can accomplish the task. |
| ingest_repoB | Ingest a repository into the code graph for tool discovery |
| scan_azure_devopsB | Scan an Azure DevOps organization for repositories with wikis and extract tool metadata from front matter |
| test_compositionB | Test a tool composition against the discovery goal using proxy implementations |
| plan_capabilities_for_goalA | Plan capabilities from discovered tools and code-graph suggestions, returning the planned tool IDs to invoke. |
| invoke_planned_toolA | Execute a planned tool returned by plan_capabilities_for_goal |
| list_candidatesB | List all registered tool candidates available for discovery |
| get_discovery_statsA | Get statistics about discovered tools and ingested repositories |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clear roles, but discover_tools and plan_capabilities_for_goal both address goal-driven tool selection, which could cause misselection. test_composition adds another layer of ambiguity about how it relates to discover_tools.
All tools follow a consistent verb_noun snake_case pattern (e.g., discover_tools, ingest_repo, invoke_planned_tool). The naming convention is uniform and predictable.
8 tools is well within the ideal 3-15 range, covering distinct stages of the discovery workflow without excess. Each tool appears to serve a necessary function.
The set covers discovery, ingestion, planning, invocation, and stats, forming a cohesive workflow. However, it lacks explicit management of registered candidates beyond Azure DevOps scanning, which could be a minor gap.