Skip to main content
Glama

find_project_for_repo

Read-only

Find the Huly workspace and project linked to a GitHub repository by owner/name, URL, or git remote, optionally scoped to a specific workspace.

Instructions

Huly workspace + project linked to a GitHub repo

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": {
      "repository": "<repository>"
    },
    "name": "find_project_for_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoDefault: search all workspaces
repositoryYesowner/name, GitHub URL or git remote

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

C2.5/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needed to add lookup-specific behavior. It adds nothing: no statement about return shape, whether it fails or returns empty on no match, or how ambiguity (multiple projects linked to one repo) is resolved. With annotations covering safety, this leaves the interesting behavior undisclosed.

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

Conciseness3/5

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

It is very short and contains no filler, but the brevity comes at the cost of a verb and any usable context; it reads as an under-specified label rather than a front-loaded explanation. Nothing is wasted, but little is delivered.

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

Completeness2/5

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

The tool is simple (2 params, no output schema, no nesting), yet the description never says what happens on zero or multiple matches or what the returned workspace/project look like. For a resolver-style lookup, that missing not-found and ambiguity behavior is the main thing an agent needs.

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%, with 'workspace' documenting the search-all-workspaces default and 'repository' documenting accepted formats (owner/name, URL, git remote). The description adds no meaning 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun fragment, 'Huly workspace + project linked to a GitHub repo', with no verb, so the agent must infer from the name that this is a lookup that resolves a repo to its workspace/project. It does name the resource pair returned, but it does not distinguish this from siblings such as get_project, which also returns project data. Purpose is inferable but not stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus get_project or project_report, no prerequisites (auth, required scopes), and no mention of what the caller should do when no repository match exists. The only hint is the parenthetical default in the schema, not the description.

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

Deploy Server

Other Tools