Skip to main content
Glama

upsert_discovery_strategy

Create or update a named discovery strategy that defines the prospect-search approach and per-strategy reply attribution. Use the slug to update it; archived=true retires it without losing data.

Instructions

Register or update a discovery strategy — the named prospect-search arm /build-list executes and add_prospects stamps for per-strategy reply attribution. Idempotent by slug: re-calling updates the approach, and any call without archived=true lands the strategy active (re-registering an archived slug revives it). archived=true retires it from registration while keeping historic attribution. Refused (400) when it would push the active count past the project's cap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesKebab-case arm id, stable for life — renaming orphans its measured history.
approachYesWhere/how to search and why it should work (2-5 lines). Platform-specific procedures belong in the playbook_<slug> document, not here.
archivedNotrue archives; omit or false lands the strategy active.
projectIdYesProject name or ID
Behavior5/5

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

With no annotations, the description carries the full burden and does so excellently. It discloses idempotency by slug, update behavior, archive/revive semantics, activation default, and the 400 refusal on exceeding the cap—providing thorough transparency beyond the schema.

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?

The description is a single, well-structured paragraph that front-loads the core purpose, then sequentially explains idempotency, archive behavior, and the cap constraint. Every sentence provides necessary information without redundancy.

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?

Given the lack of annotations and output schema, the description fully explains the tool's behavior, including edge cases (revival of archived slugs) and failure conditions (400 on cap). It covers all aspects needed for correct invocation despite the absence of structured hints.

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 description coverage is 100%, giving a baseline of 3. The description adds significant extra meaning for 'slug' (stable for life, renaming orphans history) and 'approach' (2-5 lines, playbook referral), enriching the parameter understanding beyond raw schema.

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 action: 'Register or update a discovery strategy' with a clear resource. It also distinguishes the tool by referencing how it relates to '/build-list' and 'add_prospects', making its purpose unique among siblings.

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 description explains when the tool is used (create/update a discovery strategy) and includes critical usage nuances (idempotency, archive behavior, revival, and the cap refusal). However, it does not explicitly name alternatives or state when not to use it, so it falls short of the 'explicit when-not/alternatives' criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aitit-inc/leadace'

If you have feedback or need assistance with the MCP directory API, please join our Discord server