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 project identity, AGENTS.md, memory, and discovery as one self-contained HTML page for reading or screenshotting.

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: the default collapsed rendering of AGENTS.md sections and the parallel HTTP endpoint with ?expand=all.

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?

Two dense but front-loaded sentences; the core purpose leads and the behavioral detail follows. The em-dash content list is efficient, though the second sentence packs two unrelated facts (collapse default, HTTP route) together.

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?

With no output schema, the description correctly characterizes the return value as one self-contained HTML page. Nothing critical is missing for a zero-required-parameter, read-only render tool, though it could note whether the response is the HTML itself or a reference to it.

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 description coverage is 100%, so all three parameters (theme, accent, expanded) are already documented with defaults and the accent hex format. The description only restates the expanded flag semantics, adding no new meaning beyond the schema. Baseline 3 is correct.

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 (render) and resource (the context card) and enumerates the content scope: identity, AGENTS.md, memory, discovery, output format (self-contained HTML page). An agent can distinguish this from save_context_card or read_agents_md without opening a schema.

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?

Usage is implied rather than stated: 'a person can read or screenshot' signals a human-facing, presentation use case, and it notes the equivalent HTTP route (GET /card). However, there is no explicit when-to-use, when-not, or named alternative among siblings (e.g. save_context_card vs render).

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