Skip to main content
Glama
Wolfe-Jam

mcp-context-card

by Wolfe-Jam
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

render_context_card

Render the whole project context—identity, AGENTS.md, memory, discovery—as one HTML page for reading or screenshotting. AGENTS.md sections collapse by default; pass expanded:true to open all.

Instructions

Render the whole card — identity, AGENTS.md, memory, discovery — as one self-contained HTML page a person can read or screenshot. AGENTS.md sections collapse by default; pass expanded:true for the full render. Also served at GET /card (?expand=all) over the HTTP transport.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
themeNodefault: auto
accentNoCSS hex colour, e.g. #FF702D (default: the AAIF palette)
expandedNorender every AGENTS.md section open (default: collapsed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / expanded
      Added value: +{
+  "description": "render every AGENTS.md section open (default: collapsed)",
+  "type": "boolean"
+}
  2. First observedv0.5.1

TDQS

A4.3/5.0
Behavior4/5

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

Without annotations, the description carries the burden. It discloses default collapsing behavior, the expanded parameter, and the HTTP alternative. It doesn't explicitly state read-only or side-effect-free, but 'render' implies no mutation.

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

Conciseness5/5

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

Two sentences, front-loaded with the main purpose, then additional details. No redundancy.

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?

All necessary information for invoking the tool is present: action, parameters, defaults, and alternative access method. Output format is succinctly described as an HTML page.

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?

The description adds meaning for 'expanded' by explaining the default collapse and the expanded:true toggle. The HTTP query parameter ?expand=all is also noted. Theme and accent are already well-documented in 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?

The description clearly states the tool renders the whole card as an HTML page for reading or screenshotting, listing the exact components (identity, AGENTS.md, memory, discovery). This distinguishes it from sibling tools that recall, forget, or edit individual memory sections.

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?

The description implies use for human-facing presentation but doesn't explicitly contrast with alternatives like read_agents_md or whoami. It does mention the HTTP endpoint, but lacks a clear 'when to use vs. not use' statement.

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