Skip to main content
Glama

platform_sources

Read-onlyIdempotent

List each crawl platform source with its schedule, enabled state, latest run status, pending-run count, and stalled hint so you can spot sources that are registered but idle or have not run for over 7 days.

Instructions

Crawl-platform source inventory with health and stall hints.

Every source mirrored into crawl_sources (content-repo manifests + federation members), each with: site, schedule (null = registered but not lit), enabled, the latest crawl_runs status/time/rows_written, the active pending-run count, and a stalled hint (a lit, enabled source with no run record for >7 days). Read-only.

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

Input Schema

NameRequiredDescriptionDefault
siteNorestrict the listing to one member site (e.g. "tencent").

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/openWorldHint=false, so the safety profile is covered; the description goes further by defining the derived fields an agent could not otherwise interpret — schedule null meaning "registered but not lit" and stalled meaning a lit, enabled source with no run for >7 days. It adds little on scale, ordering, or refresh cost, but the domain semantics are genuinely disclosed beyond the structured fields.

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 core purpose is front-loaded in the first line and the field enumeration that follows is dense but each item carries information. The trailing "Read-only." is redundant with readOnlyHint and the line-broken field list is slightly sprawling, but there is no filler prose.

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

Completeness5/5

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

An output schema exists and four annotations cover the safety profile, so the description only needs to frame intent and define derived fields — which it does, including the stalled heuristic and the null-schedule case. For a one-optional-parameter listing tool, nothing required to call or interpret it correctly is missing.

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 description coverage is 100% and the single optional `site` parameter is fully documented in the schema, including an example value, so the baseline 3 applies. The description text never mentions `site`, adding no filtering semantics beyond what the schema already states.

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?

"Crawl-platform source inventory" names a specific resource and read operation, and the enumerated fields (site, schedule, enabled, latest run status, pending count, stalled) make the exact shape of a row unambiguous. It implicitly separates itself from run-oriented siblings like platform_runs by returning source-level records, but it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is the tool for auditing which sources exist and which are stale, and the "stalled" definition hints at a monitoring use case. There is no explicit when-to-use, when-not-to-use, or pointer to platform_runs for per-run history.

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