Skip to main content
Glama

List Fantasy Providers

fantasy_list_providers
Read-onlyIdempotent

Supported platforms (fantrax, espn, sleeper, yahoo) with their capabilities, sports and required credentials ("what platforms does this support?"). Start here when NO profile is connected; a connected profile's leagues are already configured. League tools are read-only; sharing publishes a page only on request.

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

Input Schema

NameRequiredDescriptionDefault
response_formatNo'markdown' (default, most compact) or 'json' (same normalized data, not the raw payload).markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / response_format / description
      Previous value: -"'markdown' (default) or 'json' (raw payload)."New value: +"'markdown' (default, most compact) or 'json' (same normalized data, not the raw payload)."
  2. Changed1 schema field changed
    • changedInput schema / properties / response_format / description
      Previous value: -"Output format: 'markdown' (default, human-readable) or 'json' (raw upstream payload)."New value: +"'markdown' (default) or 'json' (raw payload)."
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds the useful framing that this is a discovery call, but its closing sentence about league tools being read-only and sharing publishing on request describes sibling tools rather than this one's behavior. Nothing is said about the shape or size of the returned platform list.

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 platform enumeration and the 'start here when NO profile is connected' cue are usefully front-loaded. However, the trailing clause about league tools being read-only and sharing publishing only on request is off-topic for a provider-listing call and dilutes the entry point. Quoted example query and parenthetical platform list add density without much cost.

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 simple, zero-required-parameter discovery tool with no output schema, the description does enough: it names the platforms and the three things returned per platform (capabilities, sports, credentials). An agent can decide to call it and knows roughly what comes back. A brief note on return size or ordering would make it complete.

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?

With one optional parameter at 100% schema description coverage, the schema already explains response_format and its enum. The description adds no information about the markdown vs json choice or when to prefer one, so it neither compensates nor detracts — baseline 3.

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 concrete payload — supported platforms (fantrax, espn, sleeper, yahoo) plus their capabilities, sports, and required credentials — so an agent knows exactly what it retrieves. It stops short of an explicit verb ('list') and does not name a sibling to contrast with, but the resource 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 Guidelines4/5

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

It gives a clear trigger: 'Start here when NO profile is connected,' and explains the inverse — a connected profile's leagues are already configured, so this call is unnecessary. That is real when-to-use guidance. What's missing is a named alternative for the 'profile already connected' case.

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