Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Request research

create_research_request
Idempotent

Starts a saved-criteria agency research workflow to find contacts for up to 200 agencies within budget, using an enabled agent and optional campaign ID; deep mode adds public-source checks.

Instructions

Starts the saved-criteria agency research workflow: up to 200 agencies and 5,000 contacts per agency, within the account's budget, using the account's enabled agent and an optional campaign_id for one of the user's own saved lists. Research uses the contact database and opened public sources; research_depth=deep adds broader public-source checks. Shared read access to another owner's list does not allow research on it. Returns the backend acknowledgment with the goal id. Delivery follows backend policy.

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": {
      "agencies": "<agencies>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_research_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
titleNo
agenciesYes
config_idNo
campaign_idNo
research_depthNostandard
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), and the description adds substantial context on top: volume caps (200 agencies, 5,000 contacts per agency), budget enforcement, which agent runs the work, the data sources used, what research_depth=deep changes, and the permission boundary on shared lists. It stops short of explaining idempotency behavior or what happens when the budget is exhausted, so it is strong but not exhaustive.

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 workflow definition and hard limits are front-loaded in the first sentence, and each subsequent sentence adds a distinct constraint or behavior. The closing line 'Delivery follows backend policy' is vague filler that consumes space without informing the agent.

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 mutating, open-world research trigger with no output schema, the description covers the important ground: cost limits, source scope, permission rules, depth modes, and the return value (backend acknowledgment with goal id). The main remaining gap is the meaning of config_id and the required idempotency_key, which an agent must guess from the schema alone.

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 0%, so the description carries the full burden. It explains agencies (cap of 200), count (5,000 per agency), campaign_id (must be the user's own saved list), and research_depth (deep adds broader public-source checks), but leaves title, config_id, and the required idempotency_key completely unexplained.

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

Purpose4/5

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

The description opens with a specific verb and resource: 'Starts the saved-criteria agency research workflow', which tells an agent exactly what is created. It implicitly separates this from the business/conference research siblings by naming 'agency' research and the agencies parameter, but it never explicitly contrasts with them.

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 supplies real preconditions — the campaign_id must reference one of the user's own saved lists, and shared read access to another owner's list does not permit research — which tells the agent when a call will be rejected. However, there is no explicit routing guidance telling the agent when to pick this over create_business_research_request, create_conference_research_request, or create_research_schedule.

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

Deploy Server

Other Tools