Skip to main content
Glama
augforce

hockey-card-analyst

by augforce

render_report

Create styled PDF reports from player assessments, comparisons, claim adjudications, or interpretive analyses. Returns the file path.

Instructions

Render an answer into a downloadable, styled PDF report; returns the absolute file path.

After completing ANY assess / compare / claim answer, ALWAYS end by asking the user if they'd like a downloadable PDF report of it — every time, as the closing line of your answer, not only when they hint at it. Generate the PDF when they say yes (or asked for a report/PDF/download up front), then give them the returned path.

result must be the EXACT structured object the engine tool just returned (assess_player / compare_players / adjudicate_claim), passed through verbatim — the same dict, not a summary of it. NEVER retype, round, rebuild, or trim fields: the server validates against the engine's own result shape and rejects anything else. If you no longer have the engine result, call the engine tool again first. Never pass the card, and never embed the card image.

kind selects the template:

  • "assess_skater": an assess_player result for a forward or defenseman

  • "assess_goalie": an assess_player result for a goalie (has danger_profile)

  • "compare": a compare_players result (works for splits and refusals too)

  • "claim_check": an adjudicate_claim result — pass the original claim sentence as title (it headlines the report and names the file)

  • "interpretive": YOUR OWN prose, for questions with no engine tool (line synergy, goalie support, free-form reads). Pass {title, tone ("positive"/"negative"/"mixed"/"neutral"), players: [names], sections: [{heading, body}, ...], caveat, summary}. The report is prominently badged "Interpretive read · AI — not an engine verdict". Never pass engine output as interpretive, and never pass your own prose under an engine kind — the badge is how the reader tells them apart.

title (optional) overrides the report heading; player names still come from the result. The PDF lands in ~/Documents/HockeyCardReports/ (created if missing; filename = player(s) + kind + date).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
titleNo
resultYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description bears full responsibility. Discloses behavior thoroughly: returns absolute file path, creates directory if missing, filename format, server-side validation of result shape, interpretive badge, and prohibition on embedding card image. This level of detail is exceptional for behavioral transparency.

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 comprehensive and logically structured, with front-loaded purpose and clear sections for usage, parameters, and examples. However, it is somewhat verbose; some sentences could be trimmed without losing meaning. Overall, every sentence earns its place given the complexity, but there is minor room for tightening.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple template kinds, strict result requirements, interactive usage), the description is highly complete. It covers all scenarios: directory creation, file naming, server-side validation, behavior for each kind, and even the interpretive badge. The presence of an output schema (noted in context signals) means return values need no further explanation, so no gap exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description adds extensive meaning beyond raw schema. It explains that 'kind' selects a template with specific valid values and behaviors, 'result' must be the exact engine output (not a summary), and 'title' is optional. For interpretive kind, it details the required nested structure. This adds significant semantic value.

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 renders an answer into a downloadable, styled PDF report and returns the file path. It specifies the verb 'render', the resource 'answer into PDF', and the output. The description also distinguishes from sibling tools by focusing on reporting/templating, not on the analysis itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides explicit instructions on when to use: after assess/compare/claim answers, always ask user if they want PDF, generate on affirmative. Details what to pass as result (exact engine object) and what not to do (never modify). Specifies template kinds and when to use interpretive. Offers clear exclusions and alternatives, fulfilling the highest standard.

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/augforce/hockey-card-analyst'

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