Skip to main content
Glama

Start a 360

start_360
Read-only

Get the link to start a free 360-degree feedback (for yourself) or a PRO campaign (to run 360s for clients or employees), with the next steps. The person answers on the website.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_360"
  }
}

Input Schema

NameRequiredDescriptionDefault
for_whomNo"myself" (default) or "others" (coaches, HR, managers)
languageNoen, fr, de or es; default en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the key behavioral fact that this only yields a link and the actual answering happens on the website ('The person answers on the website'), and that next steps are returned. It does not mention link expiry, auth requirements, or whether repeated calls create duplicate campaigns.

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?

Two short sentences, front-loaded with the outcome (get the link) and followed by the clarifying constraint. No filler; the final sentence about answering on the website earns its place as scope clarification.

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?

For a two-optional-parameter tool with no output schema, the description covers what comes back (a link plus next steps) and where the real interaction happens, which is the main ambiguity an agent would face. Remaining gaps (link lifetime, whether a new campaign is created on each call) are minor.

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% with enums on both parameters, so the schema already carries the semantics; baseline 3 applies. The description reinforces the for_whom distinction (myself vs. PRO for clients/employees) but adds nothing about the language parameter.

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 and resource — 'Get the link to start a free 360-degree feedback ... or a PRO campaign' — and distinguishes the two modes (self vs. running 360s for clients/employees). It does not explicitly name a sibling to differentiate itself from, but the action and output (a start link) are unambiguous.

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 implied through the two personas ('for yourself' vs. 'clients or employees'), which maps the agent to the for_whom choice. There is no explicit when-to-use/when-not guidance relative to check_360_status or get_product_info, so the agent must infer that this bootstraps a process rather than checking one already underway.

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