Skip to main content
Glama

DFS Lineup Optimizer

Get a lineup result

get_lineup_result
Read-only

Fetch the result of a build_lineups job that returned status 'running'. Waits up to wait_seconds; call again while status is 'running'. Jobs expire 15 minutes after they finish.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_lineup_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, non-open-world behavior, and the description adds genuinely new traits: the call blocks up to wait_seconds, must be re-invoked while running, and job results expire 15 minutes after completion. The expiry and blocking semantics are the kind of context annotations cannot convey. It does not describe what the returned result contains, leaving a modest gap.

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 short sentences, front-loaded with purpose, then the wait parameter, then the retry rule and expiry. Every sentence carries operational information with no filler.

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 should ideally hint at what the result looks like (the lineups themselves), which it does not. Everything else an agent needs to call it correctly — polling behavior, blocking semantics, job expiry — is present.

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 coverage is 0%, so the description must compensate; it does explain that wait_seconds bounds the blocking wait and that job_id refers to a build_lineups job. However, it never states the expected format/origin of job_id or the behavior at wait_seconds=0 (immediate return), so the schema's minimum/maximum constraints are not fully contextualized.

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?

States a specific verb ('Fetch') and resource ('the result of a build_lineups job') and scopes it to jobs that returned status 'running', which ties it directly to the build_lineups sibling. It does not distinguish itself from the other siblings (get_lineup_example, check_request), but the build_lineups reference gives enough to tell it apart from the job-creation tool.

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?

Explicitly gives the polling contract: 'call again while status is "running"', which tells the agent exactly how to use the tool in a loop. It implies the precondition (a prior build_lineups job) but never states an exclusion or names an alternative for retrieving past/completed lineups, so it stops short of full when/when-not guidance.

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