Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get my ICP

get_my_icp
Read-onlyIdempotent

Retrieve the account's saved ideal customer profile (ICP) targeting criteria and account profile, with an Excel download; when not saved, the download contains account metadata only. Reads only.

Instructions

The account's saved ICP (ideal customer profile): targeting criteria and account profile, with an Excel download. status not_saved means no targeting criteria are saved and the download holds account metadata only. This is the targeting definition, not the contact list. Reads only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_icp"
  }
}

Input Schema

NameRequiredDescriptionDefault
config_idNo
campaign_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so 'Reads only' adds nothing. The description does earn credit beyond the annotations by disclosing the not_saved status semantics and clarifying that the download then contains account metadata only, which is real behavioral context an agent cannot get from annotations.

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?

Four short sentences, front-loaded with the resource definition followed by the status caveat and the disambiguation. No filler, though the trailing 'Reads only' duplicates the annotations and could be dropped.

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?

There is no output schema, and the description does a reasonable job of describing the return content and the not_saved edge case. It falls short on the two unlabeled identifier parameters, which leaves an agent guessing what to pass and how the response changes with each.

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?

Both parameters (config_id, campaign_id) are optional with 0% schema description coverage, and the description never mentions them or explains how they scope the returned ICP. With the schema providing only types and defaults, the description was the only place to explain the selector semantics and it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (the account's saved ICP / ideal customer profile) and enumerates what it contains (targeting criteria and account profile plus an Excel download). It also explicitly distinguishes itself from the adjacent resource: 'This is the targeting definition, not the contact list,' so an agent can separate it from prospect/contact listing tools without opening a schema.

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 by the negative disambiguation ('not the contact list') and by the explanation of the not_saved state, which tells an agent what an empty result means. However, there is no explicit when-to-use statement and no guidance on choosing between the config_id and campaign_id parameters or on what happens when neither is supplied.

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