Skip to main content
Glama

select_project_tools

Control which generated project tools are published in the tool list using include/exclude name patterns and wildcards, with a reset option to restore the default publication policy.

Instructions

Choose which of a project's generated tools are published in the tool list. Patterns match a tool's generated name, its name without the project prefix, or (for proxied MCP tools) its upstream name; * is a wildcard. With include, exactly the matching tools are published. Unpublished tools stay callable through call_project_tool. Pass reset: true to return to the default policy.

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

Input Schema

NameRequiredDescriptionDefault
resetNoForget the selection and use the default publication policy.
excludeNoPatterns of tools never to publish.
includeNoPatterns of tools to publish, e.g. ["open_binary", "list_*"].
projectYesInstalled project: its slug, or its id such as "github:owner/name".
max_toolsNoPer-project limit on published tools (max 300), replacing the server default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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. It discloses the key mutation ('published tool list'), the default-policy fallback, and that unpublished tools are not removed but stay reachable via call_project_tool. However, it does not state precedence when both include and exclude match the same tool, whether changes persist across sessions, or what the call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then matching semantics, then the fallback behavior and reset. Dense with semicolon-chained clauses but no filler sentences; every statement carries information.

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?

A mutation tool with no annotations and no output schema needs to cover both selection semantics and consequences. It covers matching and the unpublished-tool fallback well, but leaves the include/exclude conflict rule and the observable result of the call unspecified, which matters for an agent deciding what to pass.

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 the baseline is 3; the description adds real meaning beyond it by defining what patterns match against (generated name, name without project prefix, upstream name for proxied MCP tools) and that '*' is a wildcard, plus an example pattern list. The interaction between include and exclude remains unexplained.

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?

States a specific verb and resource: choosing which of a project's generated tools are published in the tool list. It distinguishes itself from call_project_tool by explaining that unpublished tools remain callable through that sibling, so an agent can separate publication control from invocation.

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 clear context: use include to publish exactly the matching set, reset:true to return to the default policy, and notes the call_project_tool escape hatch for unpublished tools. It stops short of saying when to prefer this over the default policy or how it interacts with install/uninstall siblings.

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