Skip to main content
Glama

Partner Architect

partner_architect
Read-only

Generates a partner program with tiers, example commission amounts and KPIs from your company, product, partner model, goals and deal size to help you choose and launch the right program.

Instructions

Helps you decide what partner program to run and how to start it: it takes your company, product, partner model, partner goal and deal size, and returns a partner program with tiers, example commission amounts and KPIs. The structure differs for resellers, referrals, integrations, agencies, affiliates and white label, uses your existing partners when given, and names the partner types that fit your sector's buying committee. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of launch_commander when you need a partner program with tiers, commissions and KPIs.

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": {
      "company": "<company>",
      "product": "<product>",
      "partner_model": "<partner_model>",
      "partner_goals": "<partner_goals>",
      "your_deal_size": "<your_deal_size>"
    },
    "name": "partner_architect"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesYour company name. Format is text. For example, "invoice review service".
productYesProduct partners will sell/integrate. Format is text. For example, "invoice review service".
industryNoOptional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what it read. Format is text using one of the listed labels. For example, "logistics_tech".
your_sectorNoOptional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech".
partner_goalsYesRevenue/growth targets from partners (shown as the target of the first KPI row). Format is text. For example, "recruit three implementation partners in six months".
partner_modelYesPartner type determines program structure. Format is text using one of the listed labels. For example, "reseller".
business_modelNoOptional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, "saas".
your_deal_sizeYesAverage deal size as one amount (e.g., '$5000 ACV', '$5K' or '$500/month'; a range is refused). It scales the example commission amounts; the example rates are fixed. Format is text.
existing_partnersNoOptional: Current partner types/count, one per line or separated by semicolons (listed in the plan). Format is text. For example, "regional implementation partners".
partner_support_capacityNoHow much partner support can you provide? Format is text using one of the listed labels. For example, "minimal_self_serve".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv2.2.25
    • addedInput schema / properties / business_model
      Added value: +{
      +  "description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, \"saas\".",
      +  "enum": [
      +    "saas",
      +    "services",
      +    "connectivity",
      +    "transactions",
      +    "marketplace",
      +    "hardware_software",
      +    "investment"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / company / description
      Previous value: -"Your company name"New value: +"Your company name. Format is text. For example, \"invoice review service\"."
    • removedInput schema / properties / current_partnerships
      Removed value: -{
      -  "description": "Existing partnerships",
      -  "type": "string"
      -}
    • addedInput schema / properties / existing_partners
      Added value: +{
      +  "description": "Optional: Current partner types/count, one per line or separated by semicolons (listed in the plan). Format is text. For example, \"regional implementation partners\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / industry
      Added value: +{
      +  "description": "Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what it read. Format is text using one of the listed labels. For example, \"logistics_tech\".",
      +  "enum": [
      +    "logistics_tech",
      +    "fintech",
      +    "saas",
      +    "vertical_saas",
      +    "ai_native",
      +    "ites",
      +    "telecom",
      +    "software",
      +    "cybersecurity",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / partner_goals / description
      Previous value: -"What you want to achieve via partners"New value: +"Revenue/growth targets from partners (shown as the target of the first KPI row). Format is text. For example, \"recruit three implementation partners in six months\"."
    • addedInput schema / properties / partner_model
      Added value: +{
      +  "description": "Partner type determines program structure. Format is text using one of the listed labels. For example, \"reseller\".",
      +  "enum": [
      +    "reseller",
      +    "referral",
      +    "integration_tech",
      +    "agency_si",
      +    "affiliate",
      +    "oem_white_label"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / partner_support_capacity
      Added value: +{
      +  "description": "How much partner support can you provide? Format is text using one of the listed labels. For example, \"minimal_self_serve\".",
      +  "enum": [
      +    "minimal_self_serve",
      +    "moderate",
      +    "high_touch"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / partner_types
      Removed value: -{
      -  "description": "Types: resellers, integrations, referrals, agencies",
      -  "type": "string"
      -}
    • changedInput schema / properties / product / description
      Previous value: -"Product/service for partnership"New value: +"Product partners will sell/integrate. Format is text. For example, \"invoice review service\"."
    • removedInput schema / properties / resources
      Removed value: -{
      -  "description": "Team and budget for partner program",
      -  "type": "string"
      -}
    • addedInput schema / properties / your_deal_size
      Added value: +{
      +  "description": "Average deal size as one amount (e.g., '$5000 ACV', '$5K' or '$500/month'; a range is refused). It scales the example commission amounts; the example rates are fixed. Format is text.",
      +  "type": "string"
      +}
    • addedInput schema / properties / your_sector
      Added value: +{
      +  "description": "Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, \"logistics_tech\".",
      +  "enum": [
      +    "logistics_tech",
      +    "fintech",
      +    "saas",
      +    "vertical_saas",
      +    "ai_native",
      +    "ites",
      +    "telecom",
      +    "software",
      +    "cybersecurity",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "company",
      -  "product",
      -  "partner_goals",
      -  "partner_types"
      -]New value: +[
      +  "company",
      +  "product",
      +  "partner_model",
      +  "partner_goals",
      +  "your_deal_size"
      +]
  2. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantive context beyond them: no sign-in, no storage of inputs or outputs, hosted usage metadata being recorded, and explicit failure behavior for missing required fields or invalid values. That covers privacy, auth, and error semantics that annotations cannot express.

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?

Purpose and deliverable are front-loaded, and the operational sentences are short and scannable. A few clauses (sector buying-committee naming, the read-only/no-storage pair) are slightly redundant with each other, but each still carries distinct information.

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

Completeness5/5

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

For a ten-parameter generative planning tool with no output schema, the description supplies the missing return-value picture (tiers, commission examples, KPIs), the structural variation by model, and the error contract. Nothing an agent needs in order to call it correctly or interpret a failure appears to be absent.

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 schema already carries the field-level detail and the baseline is 3. The description goes further by explaining causal relationships: partner_model drives program structure, your_deal_size scales commission amounts while rates stay fixed, and existing_partners is folded into the plan when supplied. It only names five of the ten parameters, leaving industry/your_sector/business_model/support capacity to 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?

The opening sentence names a specific verb ('decide what partner program to run and how to start it') and lists the concrete deliverable: tiers, example commission amounts, and KPIs. It also enumerates the partner-model variants that change the output, so an agent knows exactly what class of artifact this produces.

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?

The final sentence gives an explicit routing rule: use this instead of launch_commander when the need is a partner program with tiers, commissions and KPIs. It also implies the inverse selection condition, so the agent has a concrete alternative and the discriminator for choosing between them.

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