Skip to main content
Glama

broker_search

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for paginated results (starts from 1). Use for navigating large datasets when searching broad time periods or popular collectors.
ts_endNoEnd timestamp for data collection period. Same format as ts_start. Combine with ts_start to define a specific time window for targeted BGP event analysis or research.
projectNoBGP data collection project. Options: 'routeviews' (University of Oregon RouteViews project) or 'riperis' (RIPE NCC Routing Information Service). Each has different collector locations and methodologies.
ts_startNoStart timestamp for data collection period. Accepts ISO 8601 format (e.g., '2024-08-01T00:00:00Z') or Unix timestamp. Use to find data from a specific date onwards for historical analysis.
data_typeNoType of BGP data to retrieve. 'rib' = Routing Information Base (periodic full routing table snapshots, typically every 2-8 hours, ideal for network topology analysis). 'updates' = real-time BGP routing updates (announcements/withdrawals, ideal for studying routing dynamics and outages).
page_sizeNoResults per page. Range: 1-1000, default: 100. Use larger values (500-1000) for bulk data discovery, smaller values (10-50) for quick exploration.
collector_idNoSpecific route collector identifier. Examples: 'route-views.linx' (RouteViews LINX), 'rrc01' (Amsterdam).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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.

Resources