Skip to main content
Glama

BetSlip Doctor

Share a graded ticket to Tail

share_graded_ticket_to_tail
DestructiveIdempotent

Share an owned saved Grade report to Tail with nothing to type. Call with reportId and omit confirmation to get the exact preview and previewBinding: show it to the customer. After their explicit yes, call again with confirmation PUBLISH_POST, commandKey and that previewBinding (fWarning when the preview requires it). Set shareBreakdown true on both calls to also share the Grade breakdown; the preview then shows what readers get (gradeBreakdown for a current Grade). A valid confirmed call publishes; never places a wager. Reuse its commandKey on every retry.

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": {
      "reportId": "<reportId>"
    },
    "name": "share_graded_ticket_to_tail"
  }
}

Input Schema

NameRequiredDescriptionDefault
fWarningNo
reportIdYes
showStakeNo
commandKeyNo
confirmationNo
previewBindingNo
shareBreakdownNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / shareBreakdown
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • removedInput schema / properties / reportId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description earns credit by explaining how idempotency is achieved (commandKey reuse) and what the destructive path actually does (publishes the post, and with shareBreakdown shows what readers receive). It also adds the reassurance that it 'never places a wager' and that an unconfirmed call is safe preview-only, which the annotations cannot express. It does not describe what happens on an expired previewBinding or what the confirmed response contains, which keeps this below a 5.

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?

The description is front-loaded with the highest-value instruction (preview first, nothing to type), then sequences the confirmed call, then the modifiers. Every sentence carries operational content and the parentheticals are used for conditionals rather than padding. It is dense with clauses and would benefit from the two-phase flow being broken out more visually, but there is no filler to cut.

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 destructive, seven-parameter, no-output-schema tool, the description covers the full lifecycle: preview, binding, confirmation, retry safety, and what the shareBreakdown flag visibly changes for readers. It leaves two gaps an agent would want filled, namely the meaning of showStake and the semantics of the fWarning options, but the critical irreversible-path instructions are all present.

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 description coverage is 0%, so the description carries the full burden, and it explains the intent of reportId, confirmation, commandKey, previewBinding, shareBreakdown, and fWarning, including the non-obvious point that the previewBinding must round-trip from the preview call and that shareBreakdown must be set on both calls. showStake appears in the schema but is never mentioned, and the fWarning values are not explained, so one of seven parameters and one enum's meaning remain undocumented. Strong compensation, but not complete.

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 states a specific verb and resource ('Share an owned saved Grade report to Tail'), plus the key constraint that it must be a saved Grade report the caller owns. It does not distinguish itself from the similarly named siblings preview_tail_post or publish_tail_post, so an agent must infer why this tool collapses preview and publish for this resource type, but within the definition itself 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 Guidelines4/5

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

The two-phase call sequence is spelled out precisely: first call with reportId and no confirmation to obtain the preview, then after an explicit customer yes call again with PUBLISH_POST, commandKey, and the previewBinding. Gating on 'their explicit yes' and the retry rule ('reuse its commandKey on every retry') give clear usage context. What is missing is any comparison to alternative siblings, so the guidance is rich about sequence but silent about when a different tool is the right choice.

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.