Skip to main content
Glama

Front of Goal

Get bet link

get_trade_link
Read-onlyIdempotent

The frontofgoal.com page where the user can place a bet on a match or market, with the current price of the outcome they named. Use it when the user wants to bet, or asks where to bet. The link opens our site; this tool places no bet and moves no money. Spanish (es) and Portuguese (pt) pages exist for single matches.

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": {
      "market_id": "<market_id>"
    },
    "name": "get_trade_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
outcomeNoOptional: the outcome the user wants, e.g. "Arsenal", "Draw", "Yes" or a player's name.
languageNoPage language: en, es or pt.en
market_idYesThe match or market: an id from find_matches, list_futures or get_market, or a frontofgoal.com page URL.

Output Schema

NameRequiredDescriptionDefault
urlYesThe page to open.
noteYesWhat the link does.
titleNoMarket title.
statusYesopen or closed.
outcomeNoThe outcome matched from the request.
languageNoLanguage of the page.
market_idYesMarket id.
price_centsNoApproximate cost of one share in US cents; a share pays $1 if the outcome happens.
probabilityNoIts implied probability, 0 to 1.

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 declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description nonetheless adds real value beyond them: it clarifies that the returned link opens an external site, that no bet is placed and no money moves, and that the response includes the live price for the named outcome.

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

Conciseness4/5

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

Three sentences, front-loaded with what the tool returns, then when to use it, then the safety caveat and language scope. No filler, though the opening sentence is dense and could be split for easier scanning.

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 an output schema present and a fully documented three-parameter input, the description only needs to cover scope and behavior, which it largely does. It does not say what is returned when the outcome name cannot be resolved or when a non-English language is requested for a multi-market id, a minor remaining gap.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: the link reflects the current price of the outcome the user named, which explains why outcome matters. The es/pt note also adds a real constraint (language pages exist only for single matches) beyond the enum in the schema.

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 gives a concrete verb-plus-resource: it returns the frontofgoal.com page where a bet can be placed, populated with the current price for the named outcome. That is specific enough to separate it from an odds lookup like get_match_odds, but it never names or contrasts a sibling tool directly, so it stops short of the top mark.

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?

"Use it when the user wants to bet, or asks where to bet" is an explicit, actionable trigger condition, and the note that the tool places no bet and moves no money defines a firm boundary for the agent. There is no explicit when-not or named-alternative routing, which keeps it just under a 5.

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.