Skip to main content
Glama

Visibility Genies

Set a project's client

set_project_client

Puts a site (project) under one of the workspace's clients, under a new client by name, or out of its client. Free: buys no data.

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": {
      "projectId": "<projectId>",
      "clientId": "<clientId>"
    },
    "name": "set_project_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYesThe client to put the site in, by the id list_clients gives. Null takes the site out of its client, or goes with newClientName.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
newClientNameNoA new client to add and put the site in, with clientId null.

Output Schema

NameRequiredDescriptionDefault
metaNo
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this is a bounded, non-destructive write. The description adds the useful cost trait ('Free: buys no data') but says nothing about what happens to a previously assigned client, whether repeating the call is idempotent, or any permission prerequisites for a cross-client reassignment.

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 with zero filler: the operational scope comes first and the cost trait second. Every clause carries information an agent can act on.

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

Completeness4/5

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

With full schema coverage, an output schema, and annotations covering the safety profile, the description has little left to carry. It covers the modes and cost but leaves the effect on the prior client implicit, which is the only notable gap for a state-changing tool.

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 coverage is 100%, so each parameter already documents its meaning, including the null-clientId interplay with newClientName. The description restates the same three modes in prose but adds no format or precedence detail beyond the schema, so the baseline of 3 applies.

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 names a specific verb and resource ('Puts a site (project) under one of the workspace's clients') and enumerates the three supported outcomes: assign to an existing client, create-and-assign a new client, or remove from the client. It is unambiguous about what changes, though it does not distinguish itself from any sibling tool.

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?

'Free: buys no data' gives a cost signal that helps an agent decide to prefer this over speculative paid calls, and the three mode descriptions imply when each is appropriate. There is no explicit when-not-to-use guidance or named alternative for related operations such as listing or creating clients.

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