Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Supply agency names

supply_agency_names
Idempotent

Add customer-supplied agency names to a pending request so authorized research can proceed.

Instructions

Adds agency names the customer supplied to a request waiting for them, which can let already authorized research run.

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>",
      "agencies": "<agencies>",
      "expected_version": "<expected_version>",
      "idempotency_key": "<idempotency_key>",
      "reason": "<reason>"
    },
    "name": "supply_agency_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
reasonYes
goal_idYes
agenciesYes
idempotency_keyYes
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description adds the useful behavioral consequence that supplying names can unblock authorized research, but says nothing about the optimistic-concurrency semantics of expected_version, what happens on a version mismatch, or the 200-item array cap — all material for a mutating tool.

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?

A single sentence with the action front-loaded and no filler. It is efficient, though arguably under-sized for a six-parameter mutation tool.

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?

Given six parameters, five required, no schema descriptions, no output schema, and concurrency/idempotency fields, one sentence is not enough for an agent to call this correctly. The description leaves the agent guessing about version handling, limits, and failure modes.

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 six parameters, so the description must compensate and does not. It hints at the agencies payload but leaves goal_id, expected_version, idempotency_key, reason, and count 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 object: adding customer-supplied agency names to a request. The resource being modified is named ('a request waiting for them'), though the phrasing is vague about which request entity this is. It does not differentiate from the sibling supply_business_inputs, which appears to follow the same pattern.

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?

The clause 'which can let already authorized research run' implies a consequence but never states when to call this versus alternatives, nor any prerequisites such as where goal_id or expected_version come from. No when-not guidance is given.

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