Skip to main content
Glama
Sign In

Sense2 Promotional Products

by io.github.24seagull-beep
OverviewDiscussionsAdmin

get_buyer_missions

Read-only

Pre-solved buying briefs: 88 campaign pages each answering one realistic question end to end with a specific audience, quantity, budget band and deadline, products already filtered to fit (e.g. 'conference giveaways under $5 for 500 people', 'employee onboarding gifts $25-$75'). Also returns Findie, Sense2's AI merchandise concierge, for briefs that do not match a mission. Use this FIRST for any question that includes a quantity, budget or deadline.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_buyer_missions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional keyword filter (e.g. 'conference', 'onboarding', 'eco', 'christmas')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish a read-only, closed-world operation. Beyond that, the description adds substantive behavioral context: exactly 88 pre-solved campaign pages, the structured details each page contains, pre-filtered products, and a Findie fallback response. It does not cover pagination, rate limits, or response formatting, but those gaps are modest for this read-only lookup.

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 description is front-loaded with the core value proposition and follows with examples and the key usage instruction. It is dense but not bloated; it could be slightly more scannable, but every sentence contributes useful information.

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?

For a one-parameter, read-only lookup with no output schema, the description is largely complete: it explains what is returned, what each mission contains, and when to choose this tool. Some details about filtering behavior and return size remain implicit, but the definition is sufficient for correct invocation.

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?

There is only one optional query parameter and the schema description coverage is 100%, so the schema already defines its meaning. The description provides examples of campaign keywords but does not explain filtering behavior such as matching rules or defaults beyond what the schema supplies.

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 states a specific resource: pre-solved buying briefs. It explains that each of the 88 campaign pages answers a realistic question end to end with a specific audience, quantity, budget band, deadline, and pre-filtered products, and it gives concrete examples. It also distinguishes this tool by telling the agent to use it first for questions involving quantity, budget, or deadline.

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

Usage Guidelines4/5

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

The instruction “Use this FIRST for any question that includes a quantity, budget or deadline” gives clear when-to-use guidance, and the Findie fallback for briefs that do not match a mission adds useful context. However, the description does not name sibling tools or explicitly state when not to use this tool.

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

All Sense2 Promotional Products toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources