996.fm perspective graph

Browse debates

list_debates

Read-onlyIdempotent

Browse the debate registry: id, question, readings, stance count, born (earliest publication date). Optional query: a debate matches when its question has every word of it, case-insensitive, word forms folded (hire/hiring, co-founder/cofounder). Browsing only — it does not rank against a question; use find_perspectives for that. Defaults to debates with 2+ stances, 120 rows a page — page with offset.

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

Input Schema

Name	Required	Description
`limit`	No	Rows to return (default and max 120)
`query`	No	Words the debate question must all contain (case-insensitive; word forms folded)
`offset`	No	Rows to skip — the tail line tells you the next offset
`min_claims`	No	Minimum stances on the debate (default 2)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 14, 2026

changedInput schema / properties / query / description

Previous value: -"Case-insensitive substring of the debate question"New value: +"Words the debate question must all contain (case-insensitive; word forms folded)"

First observedSep 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit for adding the default stance filter (2+), the 120-row page size, and offset paging behavior. It doesn't state result ordering, which is a minor gap for a browse tool.

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?

Front-loads what is browsed and what is returned, then the query semantics, then the routing exclusion, then defaults and paging. No sentence is wasted and the concrete folding examples (hire/hiring, co-founder/cofounder) clarify a subtle rule efficiently.

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 no output schema, the description compensates by naming the returned columns and explaining defaults and pagination. Ordering of results is the only unstated behavior an agent might care about, but otherwise it is complete for a zero-required-param browse tool.

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% — limit defaults/max, offset paging, min_claims default, and query folding are all already documented in the schema. The description restates the query matching rule (all words, case-insensitive, folded word forms) but adds no meaning beyond it, so the baseline 3 applies.

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 (browse) and resource (the debate registry) and enumerates the returned fields (id, question, readings, stance count, born). It explicitly distinguishes itself from find_perspectives, so an agent can route without opening schemas.

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

Usage Guidelines5/5

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

Explicitly states the negative case ('Browsing only — it does not rank against a question') and names the alternative to use instead ('use find_perspectives for that'). Condition and alternative are both given, leaving nothing to inference.

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

All 996.fm perspective graph tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?