Skip to main content
Glama
Sign In
@fantopy/fantopy-mcp

@fantopy/fantopy-mcp

Official
by Fantopy-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_contest

Retrieve complete details for a fantasy football contest on Fantopy Arena using its contest ID.

Instructions

Get details of a specific Fantopy contest

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contest_id": "<contest_id>"
    },
    "name": "get_contest"
  }
}

Input Schema

NameRequiredDescriptionDefault
contest_idYesThe contest ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. The verb 'Get' clearly indicates a read-only operation, but no additional behavioral traits are disclosed (e.g., what happens if the contest doesn't exist, auth requirements, or rate limits).

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?

The description is a single concise sentence with no filler or repetition. Every word earns its place.

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 one-parameter get tool, the description is adequate: it states the purpose and the schema defines the parameter. However, without an output schema or annotation, the exact nature of 'details' is vague, though not critical for such a basic read operation.

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% with the parameter 'contest_id' already described as 'The contest ID'. The description adds no further meaning beyond the schema, so the baseline of 3 is appropriate.

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?

The description clearly states the tool fetches details for a specific Fantopy contest, using a specific verb 'Get' and resource 'contest'. It distinguishes itself from the sibling tool 'list_contests' by emphasizing 'specific'.

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?

The description implies usage when you already know a contest ID ('specific contest'), but provides no explicit guidance on when to use vs. alternatives like list_contests. No exclusions or alternative tools are mentioned.

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