Skip to main content
Glama
Wolfe-Jam

mcp-context-card

by Wolfe-Jam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Render Context Card

render_context_card
Read-onlyIdempotent

Render the project's business card as one self-contained HTML page a person can read or screenshot. Front: name, title, one-liner. Flip it for the back: About, Skills (when the .fafa lists any), Context (AGENTS.md), Memory, Discovery.

Instructions

Render the project's business card as one self-contained HTML page a person can read or screenshot. Front: name, title, one-liner. Flip it for the back: About, Skills (when the .fafa lists any), Context (AGENTS.md), Memory, Discovery. layout:"portrait" for the tall view; expanded:true renders both faces flat with every section open. Also served at GET /card (?expand=all) over the HTTP transport.

Input Schema

NameRequiredDescriptionDefault
themeNodefault: auto
accentNoCSS hex colour, e.g. #0066cc (default: the .fafa metadata.cards.accent, else black/white ink)
layoutNobusiness-card view (default: landscape)
expandedNorender every AGENTS.md section open (default: collapsed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.1
    • changedInput schema / properties / accent / description
      Previous value: -"CSS hex colour, e.g. #FF702D (default: the AAIF palette)"New value: +"CSS hex colour, e.g. #0066cc (default: the .fafa metadata.cards.accent, else black/white ink)"
    • addedInput schema / properties / layout
      Added value: +{
+  "description": "business-card view (default: landscape)",
+  "enum": [
+    "landscape",
+    "portrait"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / expanded
      Added value: +{
+  "description": "render every AGENTS.md section open (default: collapsed)",
+  "type": "boolean"
+}
  3. First observedv0.5.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: output is a single self-contained HTML page intended for reading or screenshotting, sections appear conditionally ('Skills (when the .fafa lists any)'), and the same card is reachable over HTTP. It stops short of describing pagination/size limits or rendering cost.

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?

Front-loads the core purpose in the first sentence, then telegraphs options and the HTTP endpoint in dense fragments; every clause carries information. The mid-sentence parameter tips ('layout:"portrait" for the tall view') are slightly awkward to scan but cost nothing extra.

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?

No output schema exists, yet the description fully characterizes the return artifact: a single self-contained HTML page with front and back faces and named sections. Combined with annotations covering the safety profile, an agent has nothing essential missing before calling it.

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 the baseline is 3, but the description adds meaning the schema does not: 'portrait' maps to the tall view, 'expanded:true' renders both faces flat with every section open, and accent defaults to .fafa metadata.cards.accent fallback ink. Theme and the collapsed-progressive-disclosure behavior of the back face are left to the schema.

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?

States a specific verb+resource ('Render the project's business card as one self-contained HTML page') and enumerates the visible content (front: name/title/one-liner; back: About, Skills, Context, Memory, Discovery). The rendering semantics clearly separate it from the save_context_card sibling, and the agent knows exactly what artifact it produces.

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

Usage Guidelines3/5

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

Gives the reader a reason to pick options ('layout:"portrait" for the tall view', 'expanded:true renders both faces flat') and notes an alternate access path (GET /card (?expand=all)), but never states when to call this tool versus save_context_card or when the rendered card is the right answer instead of read_agents_md/list_agents_md_sections. Usage is implied rather than directed.

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

Deploy Server

Other Tools