Skip to main content
Glama
mambalabsdev

mcp-icp-fit-scorer

by mambalabsdev

Score ICP Fit

score_icp_fit
Read-onlyIdempotent

Score any company against your ideal customer profile using weighted signals. Get a 0-100 fit score, A-D tier, and per-criterion breakdown.

Instructions

Score a company against your ideal customer profile (ICP) using weighted signals. Returns a 0 to 100 icp_score, an A to D icp_tier, and a per-signal breakdown as a flat, Clay-ready JSON row. Define your ICP with a prebuilt template, a JSON scoring_config, or a plain-English icp_description (which requires llm_api_key). Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_domainYesThe primary domain of the company to score. Example: clay.com
company_nameNoOptional display name of the company.
templateNoName of a prebuilt scoring config. Alternative to scoring_config or icp_description.
scoring_configNoJSON object of scoring weights. Alternative to template or icp_description.
icp_descriptionNoPlain-English description of your target ICP. Requires llm_api_key. Alternative to template or scoring_config.
llm_api_keyNoYour OpenAI or Anthropic API key. Required only when using icp_description.
llm_providerNoLLM provider to use with icp_description: openai or anthropic.
fetch_signalsNoIf true, the actor fetches hiring and tech-stack signals for the company automatically before scoring.
include_explanationNoIf true, adds a score_explanation string to the output describing how the score was derived.
Behavior4/5

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

The description reveals key behavioral traits beyond annotations: read-only nature, requirement for APIFY_TOKEN, credit consumption, and output structure. It also clarifies the optional LLM usage for icp_description. This adds value on top of the readOnlyHint annotation. However, it does not discuss rate limits or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with two sentences. The first sentence states purpose and output; the second covers input methods and requirements. No wasted words, and key information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (9 parameters, no output schema), the description provides a good overview of inputs and outputs. It mentions the return format (icp_score, icp_tier, per-signal breakdown) and optional explanation. However, it omits details on the exact structure of the per-signal breakdown or scoring_config format, which are left to the schema. Overall, it is fairly complete.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining the relationship between template, scoring_config, icp_description, and llm_api_key. It also clarifies the purpose of fetch_signals and include_explanation. This additional context improves parameter understanding.

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 clearly states the tool's purpose: scoring a company against an ICP using weighted signals. It specifies the output format (icp_score, icp_tier, per-signal breakdown) and input options. With no sibling tools, the purpose is unambiguous and distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on how to define the ICP (template, JSON, or plain-English description) and notes prerequisites (APIFY_TOKEN, credits). It also explains optional parameters like fetch_signals and include_explanation. While it doesn't explicitly state when not to use alternatives, the guidance is sufficient given no sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mambalabsdev/mcp-icp-fit-scorer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server