Frontier Signal MCP

List buyer programmes

list_buyer_programmes

Read-onlyIdempotent

List verified buyer programmes and other sources from a public baseline, with optional filters by type, status, category, and baseline date; returns only recorded rows and never invents programmes.

Instructions

List verified buyer programmes (and other sources) from a public baseline.

Returns name, url, band, referral, categories, status, notes, and type. Filters are optional. An empty list means no rows matched — programmes are never invented.

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

Input Schema

Name	Required	Description
`type`	No	Filter by source type: buyer, lab, or seed. Omit for all.
`status`	No	Filter by exact status (case-insensitive), e.g. ok, browser-ok, dead, board-only, 200.
`category`	No	Substring match against the categories field (case-insensitive).
`observed`	No	Baseline date YYYY-MM-DD. Omit for the latest committed cut.

Output Schema

Name	Required	Description	Default
`filters`	Yes
`observed`	Yes
`programmes`	Yes
`programme_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine value with the empty-result semantics and the 'programmes are never invented' guarantee, though listing the returned fields largely restates the output 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?

The purpose and scope are front-loaded in the first sentence, and the empty-list caveat is short and earns its place. The enumerated return fields are somewhat redundant given the output schema and could be trimmed.

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 a fully described schema, an output schema, and rich annotations, the description only needs to cover scope and edge cases, which it does. The remaining gap is the absence of any routing guidance relative to the four sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all four parameters are already fully documented in the schema. The description adds only that filters are optional, which is already implied by zero required parameters, so it neither compensates nor misleads.

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?

States a specific verb and resource (list verified buyer programmes) plus the source of record (a public baseline), and notes that other source types are included. It implicitly contrasts with the singular sibling get_programme, but never names any sibling 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?

Says 'Filters are optional' and clarifies that an empty list is a valid no-match result rather than an error, which is useful invocation context. However, it gives no guidance on when to choose this over get_programme, list_observed_dates, or deltas, so the agent must infer the list-vs-lookup split from the names alone.

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

Deploy Server