Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Create research schedule

create_research_schedule
Idempotent

Schedules recurring research on specified agencies with daily or weekly cadence, setting timezone and local run time; account policies apply to each occurrence.

Instructions

Creates recurring agency research. weekday is Monday=0. The account's budget, quality and delivery policy apply to every occurrence.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
countNo
cadenceNodaily
weekdayNo
agenciesYes
timezoneNoAmerica/Chicago
config_idNo
local_hourNo
local_minuteNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds non-obvious behavior beyond that: the schedule repeats and the account's budget, quality and delivery policy are applied to every occurrence, which tells the agent this can incur repeated cost/usage. It does not say what happens on policy breach or what the response contains.

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?

Three short sentences, front-loaded with purpose, then the two pieces of information that genuinely add value (weekday indexing and per-occurrence policy). No filler or repetition of the title.

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?

This is a 10-parameter mutation with no output schema and no annotations explaining returns, so the description needs to carry more weight. It omits how cadence/count/weekday interact, what config_id selects, what the call returns (e.g., a schedule identifier), and any constraints or errors on the required agencies list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters, so the description must compensate, yet it only explains one: the weekday numbering (Monday=0). The high-impact parameters — cadence, count, timezone, local_hour/local_minute, config_id, idempotency_key and the agencies shape — receive no semantic explanation at all.

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?

"Creates recurring agency research" states a specific verb (creates), resource (research) and the distinguishing property (recurring), which separates it from the one-off create_research_request siblings. It stops short of explicitly naming an alternative, but the recurring qualifier does the disambiguation work.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance, no prerequisite note, and no reference to any sibling such as create_research_request or create_business_research_request. The agent must infer from the word "recurring" alone that this is the scheduling variant rather than a single request.

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