Skip to main content
Glama
SujayGG

pf-debate-mcp

by SujayGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

caselist_search

Find disclosed debate cases from OpenCaselist by team, debater last name, or argument text. Defaults to current HS PF caselist; specify a slug for older ones.

Instructions

Search OpenCaselist (disclosed cases) for a team, debater last name, or argument text. Defaults to the current HS PF caselist; pass a slug like 'hspf25' for older ones. Limit: 4/min.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
caselistNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • removedOutput schema / properties / result / anyOf
      Removed value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "string"
-  }
-]
    • addedOutput schema / properties / result / items
      Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
    • addedOutput schema / properties / result / type
      Added value: +"array"
  2. First observedv0.2.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it discloses the rate limit (4/min), the default scope, and the accepted search types. It does not describe result shape, but an output schema exists to cover that.

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?

Three sentences with no filler. The primary action and search options are front-loaded, the default behavior is stated, and the rate limit is appended cleanly.

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?

For a two-parameter search tool with an output schema, the description covers the essential decision points: what to search, which caselist, default behavior, and rate limiting. The only gap is lack of explicit mention of matching behavior or empty-result handling, but this is minor.

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 description coverage is 0%, so the description must compensate. It explains query as a team, debater last name, or argument text, and caselist as an optional slug with a concrete example. This is useful, though it leaves minor details like query syntax unspecified.

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?

States a specific verb ('Search') and resource ('OpenCaselist'), and names three concrete search dimensions: team, debater last name, or argument text. The phrase 'disclosed cases' clarifies scope and differentiates it from sibling tools like fetch_source or caselist_download.

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 clear context by noting the default current HS PF caselist and how to target older ones via a slug. It does not explicitly name alternatives or exclusion conditions, so it stops short of a 5.

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

Deploy Server

Other Tools