Skip to main content
Glama

platform_runs

Read-onlyIdempotent

Retrieve newest-first platform run history across all member sites, including trigger lineage for control-plane-started runs, and filter by source or row limit.

Instructions

Platform run history from crawl_runs (all member sites), newest first, with the pending_runs trigger lineage (requested_by) when the run was started from the control plane.

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_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax rows (default 20).
sourceNorestrict to one source name.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds ordering (newest first), the member-site scope, and a non-obvious data-shape detail: the pending_runs trigger lineage (requested_by) appears only when the run originated from the control plane, meaning the field is conditionally null. That conditional-column disclosure is genuinely useful context an agent cannot get from annotations or schema.

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?

One dense sentence, front-loaded with the verb-phrase equivalent ('Platform run history from crawl_runs') before the qualifiers. Internal table names like crawl_runs and pending_runs add jargon but also real provenance, so nothing feels wasted.

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?

With an output schema present, return values need no explanation, and both optional parameters are fully documented in the schema. The description covers scope, ordering, and the conditional lineage column, leaving only the relationship to sibling run-tools unspecified.

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%, with limit and source both documented inline, so the schema carries the parameter burden. The description's note that results span 'all member sites' implicitly explains why there is no site filter and why only a source filter exists, but it adds little beyond that baseline.

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?

Names a specific resource (platform run history) and its backing table (crawl_runs), plus scope (all member sites) and ordering (newest first). It does not explicitly distinguish itself from the sibling policy_runs, which reads as a parallel run-history tool, so an agent must infer the difference from the 'platform' vs 'policy' naming alone.

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 implied rather than stated: 'run history' tells an agent this is a read path for past runs, but there is no explicit when-to-use, no exclusion of policy_runs or crawl_status, and no mention of pagination or how to page past the limit. The agent must infer that policy_runs covers a different run family.

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