Skip to main content
Glama

discover_tools

Regenerate a project's toolset from executables installed in its sandbox, adding tools for hand-built or manually installed commands so they become available as typed MCP tools.

Instructions

Regenerate a project's toolset from what is currently installed in its sandbox. Pass executables (names on PATH or absolute sandbox paths) that you built or installed by hand to have tools generated for them.

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

Input Schema

NameRequiredDescriptionDefault
projectYesInstalled project: its slug, or its id such as "github:owner/name".
executablesNoExtra executables to generate tools for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key mechanic: the toolset is derived from current sandbox install state. However, it does not say what happens to previously selected or custom tools when regeneration occurs, whether the operation is additive or replaces existing configuration, or whether it is idempotent/repeatable.

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?

Two tight sentences, front-loaded with the core action and followed by the one non-obvious parameter caveat. No filler or restated title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter regeneration tool with no annotations and no output schema, the description covers the action and the optional parameter adequately but leaves the effect on existing tool configuration unstated. Given the word 'regenerate' implies replacement, that omission is the main gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so baseline is 3, but the description adds real meaning by clarifying that executables may be names on PATH or absolute sandbox paths and are for hand-built/hand-installed binaries. That resolves the ambiguity in the schema's terse 'Extra executables to generate tools for'.

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 gives a specific verb+resource: regenerate a project's toolset from the sandbox's installed executables. That is clearly distinct from read-only siblings like find_project_tools or project_info, though it never explicitly contrasts itself with select_project_tools, which an agent might reasonably confuse it with.

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 rather than stated: pass executables you 'built or installed by hand' to get tools for them, which suggests calling it after manual sandbox installs. There is no explicit statement of when to prefer this over select_project_tools or find_project_tools, and no preconditions (e.g., must the project already be installed?).

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