Skip to main content
Glama

Shareable match snippet

get_share_snippet
Read-only

Get a polished, copy-pasteable card for a 2026 World Cup match, team fixture, group standings, knockout bracket, or live matches. Returns the ready-to-paste snippet plus structured data.

Instructions

A polished, copy-pasteable card (plain text) for a match (matchId), a team's next fixture (team), a group's standings table (group, e.g. "A"), the knockout bracket (bracket: true), a date (default: today), or live matches (live: true). Returns the ready-to-paste snippet plus structured data — hand the snippet text to the user verbatim. No links; it carries a non-affiliation disclaimer, and any market line stays informational only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tzNoIANA timezone for kickoff times, e.g. America/Mexico_City
dateNoDate as YYYY-MM-DD (default: today)
langNoLocale for dates, provider attribution, and commentary: en, es, pt, fr (the summary scaffold stays English; other locales fall back to en)
liveNoSnapshot of matches in play right now
teamNo3-letter team code for that team's next fixture, e.g. MEX
groupNoGroup letter A–L for a standings card, e.g. A
styleNosocial (default, full card) or compact (one line per match)
flavorNoCommentary flair: off, subtle, full (default: full)
bracketNoKnockout bracket card (use with optional knockoutStage)
matchIdNoMatch id (most specific)
knockoutStageNoFilter the bracket card to one round
includeHashtagNoInclude the #VibingLaVidaLoca tag (default true)
includeMarketsNoInclude the reliable market line when available (default true)
includeInstallLineNoInclude the "Try it: …" run cue (default true)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
teamNo
viewNo
groupNo
stageNo
styleNo
sourceNo
tablesNo
targetNo
matchesNo
snippetNo
degradedNo
marketSignalsNo
informationalOnlyNo
Behavior4/5

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

The description adds important behavioral details beyond annotations: the tool returns a snippet plus structured data, includes a non-affiliation disclaimer, and market lines are informational. It aligns with readOnlyHint and openWorldHint.

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 a single dense sentence that efficiently conveys the tool's purpose and key behaviors. It could be broken into shorter sentences, but it is front-loaded and contains 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?

Given the 14 parameters and 0 required, the description covers the core functionality and return format. It does not address error cases, but annotations (openWorldHint) and the presence of an output schema reduce the burden.

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 100% with descriptions already present. The tool description adds minimal additional meaning to parameters beyond what the schema provides, so baseline score 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 returns a polished, copy-pasteable card for various contexts (match, team, group, bracket, date, live), distinguishing it from sibling tools by listing specific use cases and parameters.

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 description specifies when to use the tool for different snippets and instructs to hand the snippet verbatim. It does not explicitly exclude alternatives but implies usage contexts through parameter examples.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arturogarrido/claudinho'

If you have feedback or need assistance with the MCP directory API, please join our Discord server