Skip to main content
Glama

Coline

Link a place to a project

link_project_place

Links a board, channel, doc, sheet, note, folder, file, repository, mail address or link to a project. Nothing is copied.

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": {
      "workspace": "<workspace>",
      "projectId": "<projectId>",
      "kind": "<kind>",
      "refId": "<refId>",
      "label": "<label>"
    },
    "name": "link_project_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
hrefNo
kindYes
labelYes
refIdYes
projectIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
placeYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already mark this as a non-readonly, non-destructive, non-idempotent, closed-world mutation. The description adds real value with 'Nothing is copied', clarifying that this creates a reference rather than duplicating content. It does not explain what happens on a repeat link (relevant since idempotentHint=false) or what permissions are needed.

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 short sentences, front-loaded with the action and its resource list, with the key caveat ('Nothing is copied') in a distinct sentence. No filler.

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?

An output schema exists, so return values need not be described, but for a six-parameter mutation with 17% schema coverage the description leaves the core inputs (refId, href, label) unexplained and the idempotency failure mode unaddressed. It is under-specified for the tool's actual complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% — just the workspace slug is documented — so the description carries the burden and fails to. It re-lists the kinds that the kind enum already provides, but says nothing about refId vs. href (apparently required for kind='link'), what label means, or how projectId is obtained.

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?

States a specific verb (links) and enumerates the exact resource kinds being linked, then names the target (a project). Scope is unmistakable and implicitly separates it from siblings like attach_to_event/attach_to_task, though it never names those alternatives explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the verb and by 'Nothing is copied', which hints at when a reference link (rather than a copy) is appropriate. There is no explicit when-to-use/when-not guidance, no mention of prerequisites such as project membership or permissions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources