Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get research answer

get_research_answer
Read-onlyIdempotent

Retrieve a saved research answer by goal ID, including counts, findings, coverage, agencies, contacts, conference counts, and optional details or historical snapshots; read-only, starts no research.

Instructions

The compact saved answer of a research task: counts, findings, coverage, agencies and contacts in pages of five, and conference counts (roster entries, email-bearing entries and distinct addresses). details=true adds samples and dates; historical_snapshot=true reads the original goal. Missing-email causes describe only the missing-email subset. Reads only; starts no research or delivery.

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>"
    },
    "name": "get_research_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsNo
goal_idYes
agency_pageNo
source_pageNo
contact_pageNo
historical_snapshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description reinforces it with 'reads only; starts no research or delivery' while adding genuinely new behavior: results are paginated in pages of five, and missing-email causes narrow the described subset. It still doesn't say what happens past the last page or what the response envelope looks like.

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?

Front-loaded with the return contents and dense with information — no filler sentences. The main cost is a long run-on opening sentence and heavy parenthetical compression ('roster entries, email-bearing entries and distinct addresses') that takes effort to parse.

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?

With no output schema and zero schema descriptions on 6 parameters, the description does reasonably well sketching what comes back and what two flags do. It leaves gaps on per-page parameter meaning and pagination limits, which for a read-only retrieval tool is a moderate but not fatal omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 6 parameters, so the description must carry the load. It explains details=true (samples and dates) and historical_snapshot=true (original goal) and hints that agency/source/contact results are paged in fives, but it never distinguishes agency_page from source_page from contact_page individually, leaving three parameters only inferable.

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 resource — the saved answer of a research task — and enumerates its contents (counts, findings, coverage, agencies, contacts, conference counts). The closing 'starts no research or delivery' implicitly separates it from the create_research_request siblings, though it never names them.

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?

Usage is implied: fetch the persisted result of an already-run research task. The details/historical_snapshot flags give concrete reasons to call variants, but there is no explicit when-to-use vs. when-not framing, nor any pointer to a sibling such as get_task_artifact for alternative result retrieval.

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