Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get agency milestone

get_agency_milestone
Read-onlyIdempotent

Retrieve saved agency milestone metadata or one checked five-contact page for a goal, with optional milestone and page filters. Read-only; a milestone does not mean the full search is complete.

Instructions

Saved milestone metadata, or one checked five-contact page of it. A milestone does not mean the original full search is complete. Reads only.

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_agency_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
goal_idYes
milestone_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Reads only' is largely redundant. The one genuinely additive statement is the caveat that a saved milestone does not imply the original search finished — a non-obvious behavioral property worth crediting. It still does not explain what happens when milestone_id is omitted or how pagination terminates.

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 what is returned before the caveat, with no filler. The only weak sentence is 'Reads only', which restates the readOnlyHint annotation rather than adding information.

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?

With no output schema and 0% schema coverage across three parameters, the description needs to explain the return shape and parameter behavior, and it does neither beyond the vague 'metadata / one page'. An agent could not confidently construct a call for the milestone_id-null case or know what a page contains.

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% for all three parameters, so the description must carry the meaning and largely fails to. 'One checked five-contact page' loosely gestures at the page parameter's semantics but never names it or states the page cap of 3, and it does not explain that milestone_id defaults to null or what omitting it returns, nor what goal_id must reference.

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 (saved milestone metadata) and hints at a paged variant ('one checked five-contact page of it'), so an agent can roughly tell what it retrieves. However, the phrasing is oblique — 'five-contact page' is unexplained jargon — and it never contrasts itself with the sibling request_agency_first15_milestone, which appears to be the tool that generates the milestone in the first place.

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 a semantic caveat ('A milestone does not mean the original full search is complete'), which helps interpret results but is not usage guidance. Nothing states when to call this versus request_agency_first15_milestone, nor any prerequisite such as needing a goal_id from a prior search.

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