Skip to main content
Glama

Record my human's picks

save_owner_picks
Idempotent

Only for the AgentMart shop window view: when your human presses Send to my agent, the in-chat cards call it to record the slugs they ticked as the window's picks (the same picks again change nothing). Agents: never call it yourself; read the picks with get_owner_picks.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "picks": [
        "memory-locker"
      ],
      "chat_token": "shc_EXAMPLE_chat_token_example_EXAMPLE_example_"
    },
    "name": "save_owner_picks"
  }
}

Input Schema

NameRequiredDescriptionDefault
picksYesThe slugs your human ticked (empty: none of these).
chat_tokenYesThe chat token from show_shop_to_owner's result _meta (never the pick link).
passport_tokenNoNot needed on this public tool; accepted and ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chat_token / description
      Previous value: -"The chat token from the tool result's _meta (never the pick link)."New value: +"The chat token from show_shop_to_owner's result _meta (never the pick link)."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "chat_token": "shc_EXAMPLE_chat_token_example_EXAMPLE_example_",
      +    "picks": [
      +      "memory-locker"
      +    ]
      +  }
      +]
  3. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, but the description adds context annotations cannot: that it is called by the UI on the human's Send action, that repeat identical picks are a no-op, and that agents must not invoke it directly. It also pinpoints where the chat_token comes from and warns against the pick link, which is real behavioral guidance.

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?

Two tight sentences with no filler, front-loading the scope restriction and then the agent directive. The clause describing the in-chat card trigger is slightly convoluted but still parses cleanly.

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 UI-triggered write tool with only three parameters and no output schema, the definition covers caller identity, trigger condition, idempotent behavior, and the read-path alternative. Nothing material is missing for correct usage.

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 coverage is 100%, so the schema already documents picks, chat_token sourcing, and the ignored passport_token; the description adds little parameter-level meaning beyond that. Baseline 3 applies since the schema does the heavy lifting.

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 description names a specific verb and resource — recording the slugs the human ticked as the shop window's picks — and scopes it to the AgentMart shop window view. It explicitly contrasts with the sibling get_owner_picks (read) versus this tool (record), so the agent can distinguish them without opening schemas.

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?

It gives both a positive trigger (invoked by in-chat cards when the human presses Send) and an explicit exclusion ('Agents: never call it yourself'), plus the named alternative for reading picks, get_owner_picks. When-to-use, when-not-to-use, and the alternative are all stated.

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.