Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Request agency milestone

request_agency_first15_milestone
Idempotent

Queues an optional 15-contact snapshot on an existing agency task, preserving original criteria and budget without starting another research task.

Instructions

Queues an optional 15-contact snapshot on an existing agency task that covers all contacts. It keeps the original criteria and budget. It does not resume paused work, create another research task, send email or fulfill the full request.

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>",
      "expected_version": "<expected_version>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "request_agency_first15_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
goal_idYes
idempotency_keyYes
expected_versionYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true, and the description credibly reinforces the safety profile by stating what is preserved (original criteria and budget) and what is explicitly not triggered. However, it says nothing about how expected_version/expected_revision conflicts behave, how the idempotency key is deduplicated, or what a caller gets back after queuing. Useful scope context, incomplete operating semantics.

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 the core action, followed by preservation behavior and then exclusions. Every sentence contributes; only the phrase "that covers all contacts" is slightly ambiguous in its attachment.

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 mutation with a solid annotation set and no output schema, the description covers scope and non-effects adequately. The absence of any parameter explanation is the material shortfall, since four required fields with zero schema descriptions are left entirely unexplained.

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% and all four parameters are required, so the description carries the full explanatory burden. It never mentions goal_id, expected_version, expected_revision, or idempotency_key, leaving an agent to guess at concurrency and deduplication semantics. This is a significant gap for a versioned mutation.

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 states a concrete action ("queues an optional 15-contact snapshot") against a specific resource ("an existing agency task that covers all contacts"), which is far more specific than the title alone and lets an agent distinguish it from get_agency_milestone. It stops short of naming siblings, but the verb+resource+scope is unambiguous.

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?

Exclusions are explicit and useful: it does not resume paused work, create another research task, send email, or fulfill the full request. That covers the main when-not cases. It lacks a positive statement of the precondition (e.g., that a covering agency task must already exist) and does not point to the alternative to use instead.

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