Skip to main content
Glama
Sign In

Leadpoet

by com.leadpoet
OverviewDiscussionsAdmin

Get ICP fit insights

getIcpFitInsights
Read-onlyIdempotent

Summarizes what teammates' like and dislike ratings say about an ICP: patterns in the companies and contacts they rated or closed, with how many accounts or contacts support each (rated, or won, lost or disqualified; evidence[].signal says which, up to 20), minus suggestions this user dismissed.

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": {
      "params": "<params>"
    },
    "name": "getIcpFitInsights"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description adds real value beyond them: the result is aggregated evidence with per-signal support counts, evidence[].signal distinguishes rated / won / lost / disqualified, results are capped at 20, and items this user dismissed are excluded.

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

Conciseness3/5

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

It is a single front-loaded sentence with no fluff, but it is overloaded with stacked parentheticals ('rated, or won, lost or disqualified; evidence[].signal says which, up to 20'), which makes it denser than it needs to be for the single idea it conveys.

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?

With no output schema, the description does reasonable duty describing the return shape: patterns plus supporting counts, the signal discriminator on each evidence entry, and the 20-item cap. Sample size semantics ('how many accounts or contacts support each') and the dismissal filter are covered; only the icpId contract remains undocumented.

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?

The only parameter is a nested params.icpId whose schema has 0% description coverage (uuid format only). The description says results are about 'an ICP' but never explains that icpId identifies which ICP, nor any prerequisite such as the ICP existing or being visible to the user.

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 verb and resource: it 'summarizes what teammates' like and dislike ratings say about an ICP,' and it scopes the output to patterns in companies and contacts that were rated or closed. That is clearly distinct from raw-list siblings like listCompanyFitRatings, though no sibling is named explicitly.

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 or when-not-to-use statement, and no named alternative (e.g., listCompanyFitRatings for raw ratings vs. this tool for aggregate insight). The purpose implies the usage, but the agent must infer it.

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

All Leadpoet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources