Skip to main content
Glama
Sign In
DevFlow MCP Server

DevFlow MCP Server

by FaerberK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wiki_get_project_context

Get a project primer with asset counts by type, top tags, and recent updates to quickly understand project context before starting work.

Instructions

Return a brief overview of the project knowledge: number of assets per type, top-tagged categories, and recent updates. Useful as a project primer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wiki_get_project_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.35.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. It describes the tool as returning information, implying no side effects, but does not explicitly state read-only behavior or other traits.

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 two sentences and front-loads the purpose, but it omits parameter details, which would be expected even in a concise format.

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

Completeness2/5

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

Given a single parameter with zero schema coverage, no output schema, and no annotations, the description is incomplete. It explains the output but not the input, and does not cover error conditions or usage nuances.

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

Parameters1/5

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

Schema description coverage is 0% and the tool description does not mention the single parameter 'projectId' at all. No explanation of its purpose, format, or behavior if omitted.

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 it returns a brief overview of project knowledge, listing specific contents (assets per type, top-tagged categories, recent updates). The phrase 'project primer' distinguishes it from sibling tools like wiki_get_briefing or wiki_get_flow_context.

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?

'Useful as a project primer' implies when to use (quick overview), but there is no mention of when not to use or explicit alternatives among siblings.

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