Skip to main content
Glama
Sign In
MCP Teamleader Focus

MCP Teamleader Focus

by growing-pai-git
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

teamleader_add_project_owner

Assign a user as the project owner to clarify accountability and enable effective project management.

Instructions

Add a user as an owner of a project.

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": {
      "id": "<id>",
      "user_id": "<user_id>"
    },
    "name": "teamleader_add_project_owner"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe project ID
user_idYesThe user ID to add as owner

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Add', which implies a mutation, but does not mention permissions, idempotency, failure behavior, or whether adding an owner replaces existing owners.

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?

The description is a single efficient sentence with no filler or repetition. It is appropriately front-loaded, though it is quite terse and could include more operational context without becoming verbose.

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?

For a simple two-parameter mutation with fully documented schema properties, the description is minimally adequate. However, with no annotations and no output schema, it lacks behavioral context and usage guidance that would make it fully complete for an agent deciding whether and how to invoke it.

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% and both parameters have clear descriptions ('The project ID' and 'The user ID to add as owner'). The tool description adds no semantic detail beyond the schema, which aligns with the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

The description states a clear action ('Add') and resource ('a user as an owner of a project'), so an agent can understand the core operation. It does not explicitly differentiate from siblings like teamleader_assign_project or teamleader_remove_project_owner, though 'owner' provides some distinction.

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?

The description gives no guidance about when to use this tool versus alternatives such as teamleader_assign_project or teamleader_remove_project_owner. There are no context cues, exclusions, or prerequisites provided.

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