Skip to main content
Glama
Sign In

posterly

by ly.poster
OverviewDiscussionsAdmin

complete_onboarding

Idempotent

Save onboarding About you from the chat (display name, IANA timezone) and mark onboarding complete. Only when whoami says onboarding.completed is false; never re-ask once true. Then offer create_connect_session.

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": "complete_onboarding"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoWhat to call the user. A taken name gets a short suffix.
completeNofalse saves name or timezone only.
timezoneNoIANA timezone, e.g. Europe/London. Other values are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent and non-destructive, so the safety profile is covered and the description spends its space on the gate condition and the required next step, which is real added context. It does not mention that a partial save is possible when complete=false, which is a meaningful behavioral nuance hidden only in the schema.

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?

Three short sentences with zero waste: what it does, the guard condition, then the next action. The ordering mirrors how an agent would actually need the information.

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 three-parameter, all-optional call with no output schema, the description covers the entry condition and the exit step, which is what an agent needs to sequence it correctly. The one gap is the partial-save path (complete=false), which only appears in the schema and is not hinted at here.

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 the baseline is 3. The description restates the two data parameters (display name, IANA timezone) without adding format or validation detail beyond the schema, and it omits the partial-save semantics of the complete flag, so it does not meaningfully exceed the schema.

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 verb and resource: save the onboarding 'About you' fields (display name, IANA timezone) and mark onboarding complete. It also distinguishes itself from the gating sibling (whoami) and the follow-up sibling (create_connect_session), so an agent can place it in the flow without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit precondition ('Only when whoami says onboarding.completed is false') plus an explicit exclusion ('never re-ask once true'), and names the follow-up action. This is a when/when-not/next-step triple, which is the strongest form of usage guidance.

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

All posterly toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources