Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get task file

get_task_artifact
Read-onlyIdempotent

Retrieve a saved Excel artifact from a research task by goal_id and artifact_id; returns a download link valid for about ten minutes without starting research or sending email.

Instructions

A saved Excel file from a research task, with a download_url (a link valid for about ten minutes). Retrieval works even when sending is held, and never starts research, sends email or clears delivery checks.

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

Input Schema

NameRequiredDescriptionDefault
goal_idYes
artifact_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered, but the description adds genuinely new behavioral facts: the download_url expires in about ten minutes, retrieval still works when sending is held, and the call never starts research, sends email, or clears delivery checks. These side-effect exclusions and the ephemeral-link caveat are exactly the kind of context an agent cannot get from structured fields.

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 tight sentence that front-loads the return value (the file plus download_url) and then the behavioral caveats; nothing is padded. The only weakness is structural, not length — leading with a noun phrase rather than a verb makes it read like a schema fragment rather than an actionable instruction.

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?

The description usefully substitutes for the missing output schema by explaining what comes back (download_url and its ~10 minute lifetime) and what side effects do not occur. However, for a tool whose two required integer identifiers have zero schema documentation, leaving parameter meaning and error behavior unspecified is a real gap in completeness.

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 both parameters (goal_id, artifact_id) are required but entirely undocumented in the schema. The description only indirectly implies them via "from a research task" and "a saved Excel file"; it never states what an artifact_id is, how to obtain one, whether artifacts are scoped per goal, or what happens with an invalid pair. With the schema carrying no meaning, the description should have compensated and does not.

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 description identifies the resource specifically ("A saved Excel file from a research task, with a download_url"), which contrasts with the live-spreadsheet sibling, but it opens with a noun phrase rather than a verb and never states the action plainly. An agent must infer that calling this retrieves/downloads the artifact described by goal_id and artifact_id, and whether it returns file bytes or a descriptor with a link is only partially clear.

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 explicit when-to-use guidance and no named alternative, despite siblings like read_task_spreadsheet, get_task, and get_research_answer that could plausibly overlap. The single clause about working "even when sending is held" is a useful condition but addresses availability rather than tool selection.

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