Skip to main content
Glama
Sign In
@forgespace/ui-mcp

@forgespace/ui-mcp

Official
by Forge-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_project_context

Retrieve the complete project context document—including architecture, status, requirements, and roadmap—for any UIForge project using its slug.

Instructions

Returns the full context document for a UIForge project from the centralized store. This is the absolute source of truth for project architecture, status, requirements, and roadmap. Pass the project slug (e.g. "forge-patterns"). Use list_projects to discover available projects.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "get_project_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject slug to retrieve context for (e.g. forge-patterns, uiforge-webapp, uiforge-mcp, mcp-gateway)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.25.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations, so description carries full burden. Describes return as full context document and source of truth, but does not detail side effects, authentication, or potential limitations like size or rate limits.

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 concise sentences plus a third for guidance, no redundant information. Every sentence provides value.

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 no output schema, description adequately explains purpose and usage. Could detail the contents of the context document, but the 'source of truth' phrasing implies comprehensiveness.

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 already describes parameter with examples; description reinforces with additional examples (e.g., forge-patterns), adding clarity beyond 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?

Clearly states it returns the full context document for a UIForge project, specific verb 'returns' and resource 'context document'. Distinguished from siblings like list_projects and update_project_context.

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?

Explicitly states it is the source of truth and instructs to pass the project slug. Mentions using list_projects to discover available projects, providing an alternative.

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