Skip to main content
Glama

call_project_tool

Invoke any generated project tool by name—even if it is unpublished or missing from the client’s tool list—by passing the tool name and its arguments.

Instructions

Invoke any generated project tool by name, including ones that are not published in the tool list (find them with find_project_tools). Also useful when the client's tool list has not picked up newly generated tools.

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": {
      "tool": "<tool>"
    },
    "name": "call_project_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesGenerated tool name, e.g. "ruff__ruff_check".
argumentsNoArguments for that tool (find_project_tools shows its schema).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuinely useful behavioral trait — that it bypasses the published tool list and stale client caches — but says nothing about side effects, permissions, or what happens when the named tool doesn't exist or arguments don't match its schema.

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?

Two short sentences, front-loaded with the core action. The two clauses about unpublished tools and an unrefreshed tool list overlap somewhat but each targets a distinct failure mode, so the redundancy is mild rather than wasteful.

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?

The nested arguments object makes this a moderately complex indirection tool with no output schema and no annotations. The description covers routing and discovery but leaves the agent guessing about error behavior, return shape, and whether the invocation is proxied or carries the target tool's side effects.

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 both the tool name and the arguments object are already documented, including the example name format and the pointer to find_project_tools for the target schema. The description adds little beyond that, so the baseline of 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?

The description gives a specific verb and resource ("Invoke any generated project tool by name") and immediately scopes it to tools not surfaced in the published tool list. An agent can tell this apart from find_project_tools, which is named as the discovery counterpart.

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?

It states two concrete conditions for using it: the target tool is not published in the tool list, or the client's list hasn't picked up newly generated tools. It also routes discovery to find_project_tools. It stops short of explicitly saying to call the target tool directly when it is already listed, but the implied preference is clear.

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