Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Supply business inputs

supply_business_inputs
Idempotent

Fills missing criteria on an existing business research request awaiting input while preserving its saved version, revision, binding, and criteria. Same idempotency key returns the same update.

Instructions

Fills missing criteria on an existing business research request that is waiting for input (its input_required), keeping the saved version, revision, binding and existing criteria. The same idempotency_key returns the same update. It does not create a new request, add budget or start outreach.

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": {
      "goal_id": "<goal_id>",
      "spec": "<spec>",
      "expected_version": "<expected_version>",
      "expected_revision": "<expected_revision>",
      "input_binding": "<input_binding>",
      "idempotency_key": "<idempotency_key>",
      "reason": "<reason>"
    },
    "name": "supply_business_inputs"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYesThe saved partial_spec with input_required.missing_fields filled in from the customer's criteria; at most 20000 serialized JSON characters. The backend validates scope, fields and authority.
reasonYes
goal_idYes
input_bindingYes
idempotency_keyYes
expected_versionYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety and idempotency profile is largely pre-supplied. The description does add real context beyond them: it preserves the saved spec, version, revision and binding, and notes the backend validates scope, fields and authority. It does not disclose what happens on a stale version/revision or what a successful call returns, which matters for a concurrent mutation.

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?

Two dense sentences with the scope and precondition front-loaded, followed by the persistence guarantee and the explicit exclusions. No filler; the only minor inefficiency is that version/revision are listed without explaining their role.

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?

For a seven-parameter mutation with no output schema, the description covers purpose, idempotency and preserved state, which is decent. It omits optimistic-concurrency behavior for expected_version/expected_revision, the meaning of input_binding, and any indication of the response shape, so an agent would still have to guess on several required inputs.

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 only 14% across seven required parameters. The description adds meaning for essentially one of them, explaining that the same idempotency_key returns the same update, and hints at spec semantics. It says nothing about expected_version, expected_revision, input_binding, goal_id or reason, leaving most parameters to the bare schema titles and therefore failing to compensate for the coverage gap.

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 verb and resource ('fills missing criteria on an existing business research request'), pins the precondition ('waiting for input, its input_required'), and explicitly negates nearby operations ('does not create a new request, add budget or start outreach'). This lets an agent distinguish it from create_business_research_request without reading either schema.

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?

It gives a clear when-to-use condition: the request is already waiting on input and only missing fields remain. It also states what the tool is not for (creating a request, adding budget, starting outreach). It stops short of naming which sibling to call in those excluded cases, so the routing is implied rather than fully explicit.

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