Skip to main content
Glama

Prepare signup

prepare_signup

Prepare a private profile draft using information the person explicitly supplies for Syncbook. Do not query Claude memory, chat history, conversation summaries, or uploaded files. Human review is required before membership.

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": {
      "profile": "<profile>"
    },
    "name": "prepare_signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNo
profileYes
referralCodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / referralCode / maxLength
      Added value: +100
    • changedInput schema / properties / referralCode / pattern
      Previous value: -"^[a-f0-9]{24}$"New value: +"^[\\p{L}\\p{N}]+(?:-[\\p{L}\\p{N}]+)*$"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare it is a non-read-only, non-destructive write with no open-world effects. The description adds genuinely useful context — the draft is private, sourcing must come from the person, and human review is required before membership. However it never says what happens to the draft (persisted? returned? replaceable?) or whether repeated calls overwrite, which matters for a mutating tool.

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, each doing distinct work: purpose, sourcing restriction, review gate. No filler and the key constraint is front-loaded.

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

Completeness3/5

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

The schema is large and nested, there is no output schema, and annotations are minimal, so the description should do more. It covers purpose, privacy, and the review gate, but leaves unanswered what is returned, how the draft relates to preview_profile/get_signup_status, and how to populate the complex profile and context objects.

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

Parameters2/5

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

Schema description coverage is 0% with three parameters (profile, context, referralCode) and deep nesting, so the description must carry the burden — and it does not. It never mentions the context.profile provenance fields (sourceLabels, inferredFields) that the 'explicitly supplies' rule implicitly depends on, nor the referralCode, nor any required sub-fields like name/headline/offers/needs.

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 artifact: 'Prepare a private profile draft' for Syncbook signup. It is distinguishable from read-oriented siblings like preview_profile or get_signup_status by the word 'draft' and 'before membership', though no sibling is named explicitly.

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 an explicit data-sourcing rule ("using information the person explicitly supplies") plus hard exclusions — do not query Claude memory, chat history, summaries, or uploaded files. It does not say when to call this versus preview_profile or get_signup_status, so it stops short of full when/when-not/alternatives coverage.

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.