Skip to main content
Glama

find_project_tools

Read-only

Search generated tools for installed projects by keywords in names and descriptions, returning matching tool names and arguments. Use it when a project exposes more tools than the tool list shows.

Instructions

Search every tool generated for the installed projects, published or not, by keywords in its name and description. Returns matching tool names with their arguments; run them with call_project_tool. Use this for projects that offer more tools than fit in the tool list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_project_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 15, max 50).
queryNoKeywords, e.g. "open binary". Omit to list a project's tools in order.
schemaNoInclude each result's full JSON input schema (results are then limited to 5).
projectNoRestrict the search to one installed project (slug or id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real context beyond that: results include tool names with their arguments, the search spans unpublished tools too, and execution requires a separate call_project_tool step. It does not mention result ordering or pagination behavior beyond the limit parameter.

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 sentences, front-loaded with the search scope, followed by the return shape and the follow-up tool. No redundant or filler wording.

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?

With no output schema, the description still explains what comes back (matching tool names with arguments) and how to act on it. Combined with full schema coverage and a readOnly annotation, an agent has everything needed to call it correctly.

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 all four parameters are already documented, including the omit-to-list behavior and the schema=true result cap. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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 ('Search every tool generated for the installed projects') plus scope ('published or not') and the matching criteria (keywords in name and description). It also names the follow-up sibling call_project_tool, so an agent can distinguish it from discovery/listing tools without opening a schema.

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 an explicit selection condition: 'Use this for projects that offer more tools than fit in the tool list,' and routes execution to call_project_tool. It does not contrast against other discovery siblings such as discover_tools or select_project_tools, so the when-not guidance is incomplete.

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