Skip to main content
Glama

Complete the sign-up answers

complete_onboarding
Idempotent

Gives the three answers every new Prisma account gives after signing up: where you heard of Prisma, the review platforms you need and how many locations or apps you have. Use it when you created or opened the account for someone. Call again to correct them. Leave origin out if you don’t know it: it is recorded as an AI agent, or keeps the one the owner already gave.

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": {
      "platforms": "<platforms>",
      "locations_count": "<locations_count>"
    },
    "name": "complete_onboarding"
  }
}

Input Schema

NameRequiredDescriptionDefault
originNoWhere the account owner heard of Prisma. Omit if unknown.
platformsYesReview platforms to connect (google is Google Business Profile). At least one.
origin_detailNoRequired when origin is other_ai, other_search, other_directory or other: the exact name.
locations_countYesHow many locations, apps or listings.
platforms_otherNoRequired when platforms includes other: which platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a non-readonly, idempotent, non-destructive write, and the description reinforces idempotency via 'call again to correct them'. More importantly it discloses a non-obvious defaulting rule: omitting origin records it as an AI agent or preserves the owner's existing value — a side effect not visible in the schema or annotations. It does not mention auth requirements or the response shape, keeping it below a 5.

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?

Three short sentences with the core purpose front-loaded and the conditional rules following. Phrasing is slightly loose ('the three answers' while the schema has five parameters, 'the review platforms you need'), but nothing is wasted or padded.

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 five-parameter mutation with no output schema, the description covers purpose, calling conditions, re-invocation, and the key omission side effect, while the schema documents the conditional requirements for origin_detail and platforms_other. Only the return value and any account-permission prerequisites are left implicit, which is acceptable given the full schema coverage.

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

Parameters4/5

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

Schema description coverage is 100%, so a 3 is the baseline, but the description adds real meaning on top: the omit-origin default behavior (recorded as AI agent, or keeps the owner's existing value) is not stated in the schema, which only says 'Omit if unknown.' It also glosses platforms as 'the review platforms you need' and locations_count as locations, apps or listings, matching the schema's dual meaning.

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

Purpose5/5

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

States a specific action on a specific resource: submitting the three sign-up answers (origin, review platforms, locations/apps) for a new Prisma account. It is unambiguous and cannot be confused with any sibling such as create_connect_link, list_platforms, or reply_to_review.

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

Usage Guidelines4/5

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

Gives clear triggering context ('use it when you created or opened the account for someone') and explicitly covers the correction case ('call again to correct them'), which also signals idempotent behavior. It stops short of stating when not to use it, e.g. whether it is appropriate for an account the user opened themselves, so it lands just under the top band.

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