Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Request conference research

create_conference_research_request
Idempotent

Start research on a supported conference within your account limits, creating durable work with review and communication holds and no email; reuse an idempotency key for the same request.

Instructions

Starts research on a supported conference within the account's existing limits. It creates durable work with review and communication holds and sends no email. The same idempotency_key returns the same request. Returns the goal id and state.

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": {
      "event_id": "<event_id>",
      "request": "<request>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_conference_research_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
event_idYes
config_idNo
research_depthNostandard
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: durable work, review and communication holds, and explicitly 'sends no email' — a critical side-effect disclosure for an openWorldHint mutation. It also restates idempotency with concrete meaning (same key returns the same request) and discloses return values (goal id and state), though it says nothing about quota-exceeded or hold-release behavior.

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?

Four short sentences, front-loaded with the action and scope, then side effects, then idempotency, then return value. Only 'within the account's existing limits' is filler-adjacent vagueness that doesn't resolve to anything actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the essentials an agent needs to call safely — no email sent, work is durable and held for review, idempotent retry semantics, and the return shape despite no output schema. However, for a 5-parameter mutation with zero schema description coverage, config_id and research_depth remain opaque, and 'existing limits' is never quantified.

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 5 parameters, so the description carries the full burden and only covers idempotency_key meaningfully. event_id is hinted at via 'supported conference', but request, config_id, and research_depth (including the standard/deep choice) are left entirely 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?

States a specific verb and resource: 'Starts research on a supported conference.' The word 'conference' and the event_id enum distinguish it from the business/general research siblings well enough for an agent to pick correctly, though the description never names those siblings outright.

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?

'within the account's existing limits' implies a quota gate but never defines it, and there is no explicit when-to-use/when-not or routing statement against create_business_research_request or create_research_request. Usage is implied by the resource scope rather than stated.

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