Skip to main content
Glama

Confirm brand during setup

flypost_confirm_onboarding_brand

Save the brand found on their website once the user has checked it. Pass only what they corrected. If the website could not be read, pass company_name and product_description from the user.

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

Input Schema

NameRequiredDescriptionDefault
project_idNoProject (workspace) id. Omit to use the active project, or the only project if there is just one.
company_nameNoCompany name, if the one found was wrong or missing.
target_audienceNoWho they sell to, if corrected.
product_descriptionNoOne line on what they do, if corrected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already establish that this is a non-destructive write in a closed context. The description adds useful confirmation semantics by saying to pass only what the user corrected, but it does not explain merge/overwrite behavior, idempotency, or what is saved when no fields are supplied.

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, front-loaded with the primary action and followed by the correction and fallback rules. There is no redundant or filler language.

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?

The definition covers the main onboarding confirmation flow, the minimal-correction rule, and the website-read failure path. It is reasonably complete for a 4-parameter, optional-field write tool with no output schema, though it could clarify how this interacts with final onboarding completion.

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 coverage is 100%, so the baseline is 3, but the description adds conditional meaning: only corrected fields should be sent, and company_name plus product_description are the fallback when the website could not be read. project_id is left to the schema, which already documents it.

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 states a specific action ('Save the brand found on their website') and the confirmation condition ('once the user has checked it'). It is clearly a brand-confirmation step, though it does not explicitly distinguish itself from nearby tools such as update_brand_kit or finish_onboarding.

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?

It gives clear timing guidance ('once the user has checked it') and a fallback case ('If the website could not be read, pass company_name and product_description'). It does not name alternative tools or explain when not to use this tool, so it falls short of explicit sibling routing.

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.