Skip to main content
Glama

list_research

Read-onlyIdempotent

What has Coil published in its research studies? Coil's published research: the studies behind the rules, including the ones that failed. The Coil Edge Research index: every published backtest study with its question, pre-registered verdict, evidence class, data window and per-read price, plus the address of each full paid text. Free and keyless; the studies themselves are sold one read at a time over x402.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses genuinely useful operational facts: the call is free and keyless, and the underlying studies are paid per-read via x402. It also previews the shape of each record. It stops short of covering ordering, pagination, or result size, which for an index-style list tool is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The field inventory is dense and valuable, but the opening question ('What has Coil published in its research studies?') restates the following sentence, and 'the studies behind the rules, including the ones that failed' is brand flavor rather than operational detail. The pricing/access information would be better front-loaded instead of trailing the field list.

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 carries the burden of describing returns, and it does so by enumerating the fields per study plus the access model. For a zero-parameter, read-only index tool that is close to sufficient; only ordering, cardinality, and format are left unstated.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the schema is fully self-describing. Baseline of 4 applies; the description does not need to compensate for anything here.

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?

The description names the specific resource (Coil Edge Research index of published backtest studies) and enumerates what each entry carries: question, pre-registered verdict, evidence class, data window, per-read price, and the address of each paid text. It is slightly indirect because it opens with a rhetorical question rather than a verb+resource statement, and it does not explicitly contrast itself with siblings, but the purpose is unambiguous.

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?

Guidance is implied rather than stated: 'Free and keyless' tells the agent it can call this without credentials, and the note that studies are 'sold one read at a time over x402' signals that this tool only lists the index rather than delivering content. There is no explicit when-to-use/when-not-to-use rule and no named alternative from the sibling set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources