Ready APIs

Site Risk Bulk Rank

intel_rank

Read-onlyIdempotent

Score and rank up to 100 ZIPs against a single site profile. Returns sorted by risk_score (highest = lowest risk).

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": {
      "candidates": "<candidates>"
    },
    "name": "intel_rank"
  }
}

Input Schema

Name	Required	Description	Default
`candidates`	Yes	Up to 100 five-digit US ZIPs.
`site_profile`	No		insurance_underwriting

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 14, 2026

TDQS

A4.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 behavior. The description adds valuable behavioral context beyond that: results are sorted by risk_score and higher scores mean lower risk.

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?

Two sentences efficiently deliver the action, the constraint on input size, the comparison basis, and the output ordering/interpretation. No filler or redundancy.

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 bulk ranker with rich annotations and only two parameters, the description is largely sufficient. The key missing details are risk_score range and how invalid ZIPs are handled, but the core contract is clear.

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 schema documents candidates and enumerates site_profile values, covering 50% of parameters. The description clarifies that the profile is single and applied across all candidates, but it does not explain profile semantics, risk_score range, or invalid-input behavior.

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 action ('Score and rank'), a bounded resource ('up to 100 ZIPs'), and a comparison basis ('a single site profile'). It clearly distinguishes itself from single-lookup tools like site_risk and batch location tools like geo_zip_batch.

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 intended use is clear: bulk-rank ZIPs against one site profile. It does not explicitly name alternatives or state when not to use it, so it falls just short of a full 5.

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

All Ready APIs tools Inspect

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

Need Help?