scry_check_bulk
Look up many IPv4 addresses in one request. Up to 100 IPs per call. Same per-IP shape as scry_check, keyed by IP.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ips | Yes |
Scry
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses limit and output shape relative to scry_check, but no annotations exist so description carries full burden. Missing details on idempotency, 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?
Two concise sentences with no filler. Front-loaded with action and key constraint.
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?
No output schema, but references scry_check for per-IP shape. Adequate for a bulk lookup tool, though could mention per-IP error handling.
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?
Schema has 0% description coverage; description adds that parameter is IPv4 addresses and keyed by IP, but lacks format details or examples. Minimal added value beyond schema.
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?
Clearly states 'Look up many IPv4 addresses in one request' with specific verb and resource, and distinguishes from sibling 'scry_check' by noting same per-IP shape.
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?
Provides usage limit (up to 100 IPs) and implies when to use bulk vs single via reference to scry_check. Could explicitly state 'use scry_check for single IP' but implied adequately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation5/5
Each tool targets a unique resource or operation: single IP lookup, bulk IP lookup, ASN roll-up, country roll-up, campaign detail, campaign list, recent observations, stats, timeseries, tool detail, tool list, and top sources. There is no overlap or ambiguity, and descriptions explicitly state when each tool should or should not be used.
Naming Consistency5/5
All tool names follow the consistent pattern 'scry_' plus a descriptive noun (e.g., scry_asn, scry_check, scry_timeseries). The naming is uniform, lowercase with underscores, and logically reflects the tool's purpose.
Tool Count5/5
With 12 tools, the set is well-scoped for a threat intelligence server. It provides sufficient granularity without being overly large or sparse, covering core functionality without redundancy.
Completeness5/5
The tool surface covers key operations for IP triage, campaign analysis, statistical overviews, time-series trends, and tool detection. There are no obvious gaps; all common use cases for network observation and threat intelligence are addressed.