Skip to main content
Glama

Pinpoint Value

impact_pinpoint_value
Read-only

Generates believable value statements and ranked proof points from your target customer, key outcome, and unique capability, plus audience/channel versions and test questions.

Instructions

Helps you decide what you can claim that buyers will believe. You give your target customer, the main outcome they get and what you do that others do not, plus optional product name, category, customer results and business model. You get value statements in three versions, a value matrix for your own figures, proof points ranked from customer results to social proof, versions for different audiences and channels, and questions to test the value. 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 impact_craft_message when you need outcome and proof statements before writing the core message.

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": {
      "target_customer": "<target_customer>",
      "key_outcome": "<key_outcome>",
      "unique_capability": "<unique_capability>"
    },
    "name": "impact_pinpoint_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoProduct category. Format is text. For example, "manufacturing".
key_outcomeYesThe main result customers achieve. Format is text. For example, "resolve invoice exceptions before month-end".
your_sectorNoYour 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".
product_nameNoYour product/company name. Format is text. For example, "invoice review service".
business_modelNoHow you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used to choose proof types; read from your inputs when not given. Format is text using one of the listed labels. For example, "saas".
target_customerYesWho you serve (e.g., "cloud security leads at mid-size fintech companies"). Format is text.
customer_metricsNoAny customer results data (e.g., "critical exposures down 70% in one quarter; audit preparation from 3 weeks to 4 days"). Format is text.
unique_capabilityYesWhat you do that others cannot/don't. Format is text. For example, "checks invoice exceptions before approval".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.2.28
    • addedInput schema / properties / business_model
      Added value: +{
      +  "description": "How you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used to choose proof types; read from your inputs when not given. 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 / category / description
      Previous value: -"Product category"New value: +"Product category. Format is text. For example, \"manufacturing\"."
    • changedInput schema / properties / customer_metrics / description
      Previous value: -"Optional: Any customer results data (e.g., \"40% faster, 3x pipeline\")"New value: +"Any customer results data (e.g., \"critical exposures down 70% in one quarter; audit preparation from 3 weeks to 4 days\"). Format is text."
    • changedInput schema / properties / key_outcome / description
      Previous value: -"The main result customers achieve"New value: +"The main result customers achieve. Format is text. For example, \"resolve invoice exceptions before month-end\"."
    • changedInput schema / properties / product_name / description
      Previous value: -"Your product/company name"New value: +"Your product/company name. Format is text. For example, \"invoice review service\"."
    • changedInput schema / properties / target_customer / description
      Previous value: -"Who you serve (e.g., \"B2B sales teams\")"New value: +"Who you serve (e.g., \"cloud security leads at mid-size fintech companies\"). Format is text."
    • changedInput schema / properties / unique_capability / description
      Previous value: -"What you do that others cannot/don't"New value: +"What you do that others cannot/don't. Format is text. For example, \"checks invoice exceptions before approval\"."
    • addedInput schema / properties / your_sector
      Added value: +{
      +  "description": "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"
      +}
  2. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, and the description adds real context beyond them: no sign-in, no storage of inputs or outputs, hosted usage metadata recorded, and errors that name the missing or invalid field. The only gap is that it doesn't say how large the returned payload is or whether output is deterministic.

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?

Front-loaded with the purpose and the input/output summary, and every sentence carries information. There is mild redundancy between 'Read-only for business data' and 'needs no sign-in and stores no inputs or outputs', and the single long sentence listing outputs could be split for scanability.

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?

With no output schema, the description compensates by enumerating the returned artifacts (three value-statement versions, matrix, ranked proof points, audience versions, test questions) and the error behavior. It is nearly complete, though it doesn't state whether the value matrix requires customer_metrics to be useful.

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 description coverage is 100%, so the schema already documents all eight parameters including the two enums. The description restates the main inputs and optional ones but adds no format or interaction detail, and it omits your_sector entirely, so it does not meaningfully exceed the schema baseline.

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: it produces value statements, a value matrix, ranked proof points, audience/channel versions and test questions from a target customer, outcome and unique capability. It also names the sibling it replaces (impact_craft_message), so an agent can distinguish it without opening the 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?

Explicitly says to use this instead of impact_craft_message when outcome and proof statements are needed before writing the core message, giving both the condition and the alternative. It also states the three required inputs, so the agent knows the minimum to supply.

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