Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get started with ProducerSpark

get_started
Read-onlyIdempotent

Review account capabilities and free-trial prospect balance before searching; see agents, search permissions, campaigns, next step, and results/upgrade links without charges.

Instructions

What this account can do right now: the agents on the account (and those not on it), free_prospects (granted, used, remaining) on the free trial, can_search_people, example_requests, campaigns (each with its name, status, three steps and Golden List), has_campaign, next_step, first_name, results_url (the account's ProducerSpark page with every search and its Excel download) and upgrade_url (plans). Reads only; nothing is searched or charged.

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_started"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds a genuinely useful cost/scope note ('nothing is searched or charged') that annotations cannot express, and it enumerates the shape of the result since no output schema exists. However, it does not explain how fields relate — e.g. what next_step returns, whether free_prospects remaining is a live counter, or whether results_url is always present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loading the scope ('What this account can do right now') is good, and the closing constraint is well placed. But the body is one long run-on sentence with nested parentheses that reads as a field dump — splitting it into 'what it returns' and 'what it does not do' would make it far easier to parse without losing content.

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?

With no output schema and no parameters, the description carries full responsibility for revealing the return payload, and it does enumerate the salient fields (agents, free_prospects quota, campaigns with status and steps, results_url, upgrade_url). It is close to complete for a zero-input onboarding tool, missing only the semantics of individual fields such as next_step and has_campaign.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The field inventory describes outputs, not inputs, so no parameter-level gaps exist.

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

Purpose3/5

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

The opening clause 'What this account can do right now' signals an onboarding/account-state snapshot, but the description is a comma-separated inventory of returned fields rather than a stated verb+resource purpose. An agent can infer it is a read-only status tool, yet nothing explicitly says 'returns the account's onboarding state and quotas' — the purpose must be reconstructed from the field list.

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 guidance: no statement that this should be called first, on session start, or when the account state is unknown. No alternative is named, even though siblings like get_campaign_results or get_prospect_list overlap conceptually. The only routing signal is the closing 'nothing is searched or charged', which implicitly points away from the search tools.

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