Skip to main content
Glama

Create a playbook

create_playbook

Create a negotiation playbook defining preferences for each clause: preferred option, flexibility (1-5), red lines, and acceptable alternatives.

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": {
      "name": "<name>",
      "contractType": "<contractType>",
      "governingLaw": "<governingLaw>",
      "entries": "<entries>"
    },
    "name": "create_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUnique playbook name
entriesYes
contractTypeYesContract type code: one from list_contract_types, or an A2A_ agent-to-agent protocol type from list_templates (those are negotiated only, never made with generate_contract)
governingLawYes
contractLanguageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / entries / items / properties / priority
      Removed value: -{
      -  "maximum": 5,
      -  "minimum": 1,
      -  "type": "integer"
      -}
  2. Changed1 schema field changed
    • changedInput schema / properties / governingLaw / enum
      Previous value: -[
      -  "CALIFORNIA",
      -  "ENGLAND_WALES",
      -  "SPAIN",
      -  "DELAWARE"
      -]New value: +[
      +  "CALIFORNIA",
      +  "UNITED_STATES",
      +  "ENGLAND_WALES",
      +  "SPAIN",
      +  "DELAWARE"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / governingLaw / enum
      Previous value: -[
      -  "CALIFORNIA",
      -  "ENGLAND_WALES",
      -  "SPAIN"
      -]New value: +[
      +  "CALIFORNIA",
      +  "ENGLAND_WALES",
      +  "SPAIN",
      +  "DELAWARE"
      +]
  4. Changed3 schema fields changed
    • changedInput schema / properties / contractType / description
      Previous value: -"Contract type"New value: +"Contract type code: one from list_contract_types, or an A2A_ agent-to-agent protocol type from list_templates (those are negotiated only, never made with generate_contract)"
    • removedInput schema / properties / contractType / enum
      Removed value: -[
      -  "A2A_API_ACCESS",
      -  "ACTA_CONSEJO_ADMINISTRACION",
      -  "ACTA_JUNTA_GENERAL",
      -  "ADVERTISING_IO",
      -  "ADVISORY",
      -  "AFFILIATE_PROGRAM",
      -  "A2A_MONITORING",
      -  "PHANTOM_SHARES_GRANT",
      -  "RESIDENTIAL_TENANCY_GB",
      -  "RESIDENTIAL_TENANCY_US_CA",
      -  "DELAWARE_CERT_OF_INCORPORATION",
      -  "A2A_COMPUTE_PROCUREMENT",
      -  "CONSULTING",
      -  "A2A_CONTENT_LICENSE",
      -  "RESIDENTIAL_TENANCY_ES",
      -  "CONVERTIBLE_NOTE",
      -  "DATA_LICENSING",
      -  "DPA",
      -  "A2A_DATA_SHARING",
      -  "EMPLOYMENT",
      -  "CONTRATO_LABORAL",
      -  "EQUITY_INCENTIVE",
      -  "FOUNDERS",
      -  "BAA_NEGOTIATOR",
      -  "CESION_PI",
      -  "IP_ASSIGNMENT",
      -  "INFLUENCER_MARKETING",
      -  "JOINT_VENTURE",
      -  "A2A_KNOWLEDGE_ACCESS",
      -  "PHANTOM_SHARES_PLAN",
      -  "A2A_MARKETPLACE",
      -  "MSA",
      -  "NDA",
      -  "A2A_ORCHESTRATION",
      -  "A2A_PAYMENT_AUTHORIZATION",
      -  "PRIVACY_NOTICE",
      -  "SAFE",
      -  "SAAS",
      -  "SEED_INVESTMENT",
      -  "CONTRATO_SERVICIOS",
      -  "SHAREHOLDERS",
      -  "PACTO_SOCIOS",
      -  "SOFTWARE_DEVELOPMENT",
      -  "A2A_SUPPLY_CHAIN",
      -  "A2A_TASK_DELEGATION",
      -  "TECHNOLOGY_LICENSE",
      -  "TEMPLATE",
      -  "TERM_SHEET",
      -  "A2A_TOOL_LICENSE",
      -  "WHITE_LABEL_RESELLER"
      -]
    • changedInput schema / properties / governingLaw / enum
      Previous value: -[
      -  "CALIFORNIA",
      -  "NEW_YORK",
      -  "ENGLAND_WALES",
      -  "SPAIN"
      -]New value: +[
      +  "CALIFORNIA",
      +  "ENGLAND_WALES",
      +  "SPAIN"
      +]
  5. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description usefully adds the shape of what gets created (per-clause preferences with a bounded flexibility scale and red-line flags). It says nothing about name-uniqueness conflicts, whether a playbook is reusable across negotiations, or what happens on invalid clause/option IDs, which matters for a mutation 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?

One front-loaded sentence with the action first and the field enumeration second; every clause carries information and there is no filler or restatement of the title beyond the leading verb phrase.

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?

For a 4-required-parameter mutation with no output schema, the description covers the payload concept but omits identifier provenance, duplicate-name behavior, and any error/conflict expectations. Adequate to attempt a call, not adequate to call it correctly on the first attempt in edge cases.

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 only 40% and the entire entries item sub-schema (clauseId, preferredOptionId, isRedLine, flexibility, acceptableOptions) has no field descriptions; the description meaningfully compensates by naming each of those concepts and the 1-5 flexibility scale. It leaves governingLaw and contractLanguage unaddressed, and doesn't say where clauseId/preferredOptionId values originate.

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 resource ('Create a negotiation playbook') and immediately enumerates the per-clause content (preferred option, flexibility 1-5, red lines, acceptable alternatives), which makes the tool's output distinguishable from generate_contract or initiate_negotiation. It stops short of naming a sibling or explaining how the playbook relates to negotiation tools.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance, no prerequisites, and no routing to alternatives such as initiate_negotiation. The only routing hints (list_contract_types, list_templates, 'never made with generate_contract') live in the schema's contractType field, not in the description.

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.