Skip to main content
Glama

Panel: offer to show

personal_offer

Shows a one-time in-app offer when a user selects Personal data in the results panel for anonymised totals or profile moments.

Instructions

The user reached for something of Personal's in the results panel (moment "anonymised_or_totals" or "profile"): the offer to show there, the first time only. App-only.

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": {
      "moment": "<moment>"
    },
    "name": "personal_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
momentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already disclose that this is a non-destructive, non-read-only, closed-world operation. The description adds useful behavioral constraints beyond them: "first time only" and "App-only". It does not say what state changes or what gets returned, so it remains thin.

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?

The definition is short and has no filler; the trigger conditions are front-loaded before the "App-only" constraint. The phrasing is awkwardly compressed, but that is a clarity issue rather than excessive length.

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

Completeness2/5

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

For a simple one-parameter tool there is no output schema, yet the description still leaves the core action, side effects, and response shape unclear. The annotations cover safety hints, but they do not compensate for the missing explanation of what calling the tool actually does.

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?

With 0% schema description coverage, the description partially compensates by naming two likely allowed values for the single required parameter: "anonymised_or_totals" or "profile". It still does not explain the meaning of "moment" or state whether those are the only valid values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description largely restates the title/name with a narrative trigger: "the offer to show there". It never states a clear action verb or explains what the tool actually does when invoked, and the referent "Personal's" is undefined.

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

Usage Guidelines3/5

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

It implies when the tool is relevant by naming the user action in the results panel and the moments "anonymised_or_totals" or "profile", plus the "first time only" condition. However, it is narrative context rather than explicit when-to-use guidance and does not distinguish from siblings like dismiss_offer.

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