After using the `repo_create_pull_request` tool, the LLM often displays an incorrect project in the pull request URL

[Meir017]

For example:

My repository is in the msazure/MCAS project, however the LLM often uses the One project (probably due to it being a very common one)

I think that adding the project name to the response would solve this.

azure-devops-mcp/src/tools/repositories.ts

Lines 116 to 134 in 20deed7

	function trimPullRequest(pr: GitPullRequest, includeDescription = false) {
	return {
	pullRequestId: pr.pullRequestId,
	codeReviewId: pr.codeReviewId,
	repository: pr.repository?.name,
	status: pr.status,
	createdBy: {
	displayName: pr.createdBy?.displayName,
	uniqueName: pr.createdBy?.uniqueName,
	},
	creationDate: pr.creationDate,
	closedDate: pr.closedDate,
	title: pr.title,
	...(includeDescription ? { description: pr.description ?? "" } : {}),
	isDraft: pr.isDraft,
	sourceRefName: pr.sourceRefName,
	targetRefName: pr.targetRefName,
	};
	}

adding

function trimPullRequest(pr: GitPullRequest, includeDescription = false) {
  return {
    pullRequestId: pr.pullRequestId,
+   project: pr.repository?.project?.name,
    codeReviewId: pr.codeReviewId,
    repository: pr.repository?.name,

[danhellem]

I will take a look. Thanks for the information

[Meir017]

My current workaround is to have the llm run git remote get-url origin.

I noticed that the llm can sometimes also hallucinate the org name

[danhellem]

Fixing in #803. Going to close this issue and just waiting for merge