Skip to main content
Glama
Sign In

RanklyBee

by io.github.dazhiyu0235
OverviewDiscussionsAdmin

Get a prospect discovery job

get_prospect_discovery
Read-only

Read the progress and result counts of a discovery job.

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": {
      "projectId": "<projectId>",
      "siteId": "<siteId>",
      "jobId": "<jobId>"
    },
    "name": "get_prospect_discovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
siteIdYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral detail by saying it returns progress and result counts, but it does not explain job states, error behavior, or the shape of the returned progress data.

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 a single front-loaded sentence with no wasted words. It is efficient and immediately states the tool's output focus.

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?

Given three required but completely undocumented identifiers and no output schema, the description is too thin to guide correct invocation. It covers the basic purpose but omits parameter meanings, return details, and any usage context relative to sibling tools.

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

Parameters1/5

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

All three required parameters have zero schema description coverage, and the description does not explain what projectId, siteId, or jobId mean or how they relate. For a tool with fully opaque identifiers, this leaves the agent with no semantic guidance beyond the parameter names.

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?

The description states a specific verb and resource: reading the progress and result counts of a discovery job. It is clear what the tool does, but it does not distinguish itself from nearby tools such as get_prospect_discovery_settings or get_prospecting_summary.

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 guidance on when to use this tool versus alternatives, nor any stated prerequisites or exclusions. The agent is left to infer usage context entirely from the tool name and sibling list.

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

All RanklyBee 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