Skip to main content
Glama
Sign In

Leadpoet

by com.leadpoet
OverviewDiscussionsAdmin

Count drafts awaiting review

getReviewSummary
Read-onlyIdempotent

Counts the drafts held in Review for a decision by quality band: review_ready (passed the quality check), needs_revision (an edit would fix it) and unusable (no usable quality check, or it failed). Gives the most common reasons in each band and the counts per campaign. Filter by campaign_id. Saves nothing. It counts only drafts held for a decision, so a total of 0 does not mean Review is empty; Review also lists saved drafts of contacts whose draft could not be prepared, read from listReview, and replies to answer, read from listReplies.

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": "getReviewSummary"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds important semantic context: what counts, what does not count, how quality bands are defined, and why a zero total can be misleading. It does not describe the exact response shape, but it goes well beyond the safety profile in the 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?

The description is dense but front-loaded: it begins with the counting purpose and bands, then adds reasons and campaign counts, then the filter, then the zero-total caveat. Every sentence carries useful information, though the long final sentence is somewhat packed.

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?

For a read-only count tool with one optional nested parameter and no output schema, the description gives enough context to call it correctly and interpret the counts. It defines bands, exclusions, and sibling alternatives, though it could be slightly more explicit about the return structure.

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

Parameters3/5

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

The description says to filter by campaign_id, which identifies the only meaningful nested field. However, it does not explain the surrounding query object, that the parameter is optional, or the UUID format, and with schema description coverage reported as 0% it compensates only partially.

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 states a specific verb and resource: it counts drafts held in Review for a decision, broken out by quality band, reasons, and campaign. It also distinguishes this tool from listReview and listReplies by naming what those siblings cover instead.

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

Usage Guidelines5/5

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

The description explicitly scopes usage to drafts held for a decision and warns that a total of 0 does not mean Review is empty. It then routes the agent to listReview for saved drafts that could not be prepared and to listReplies for replies to answer, giving clear alternatives.

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