Skip to main content
Glama

The Local Upgrade — Software Engineering

Prepare a structured project brief

prepare_engagement_brief
Read-onlyIdempotent

Formats confirmed business requirements for an RFP or proposal request. Does not store, transmit, quote or approve the project. Preserve unknowns; no technology or budget ceiling.

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": {
      "title": "<title>",
      "businessOutcome": "<businessOutcome>",
      "engagementType": "<engagementType>",
      "requirements": "<requirements>"
    },
    "name": "prepare_engagement_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
constraintsNo
requirementsYes
budgetContextNoNot specified
openQuestionsNo
engagementTypeYes
businessOutcomeYes
existingSystemsNo
timelineContextNoNot specified
acceptanceCriteriaNo
procurementRequirementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive operation, and the description adds real context on top: it explicitly disclaims storing, transmitting, quoting or approving, which tells the agent the output is an inert document rather than an action. The constraint 'no technology or budget ceiling' and 'Preserve unknowns' further disclose output-shaping behavior (do not invent scope or fill gaps) that annotations cannot express. It omits any statement about what the returned brief looks like or how failures are reported, keeping it below a 5.

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?

Three short sentences, with the core action front-loaded before the negative scope and the constraint notes. It is efficient, but the final fragment 'Preserve unknowns; no technology or budget ceiling' is telegraphic enough to be ambiguous about which field it governs.

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?

For an 11-parameter tool with zero schema description coverage and no output schema, the description is materially incomplete: an agent knows what the tool produces conceptually but not how to populate nearly any field. Given the complexity of an RFP brief, this leaves too much of the calling contract undocumented.

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

Parameters2/5

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

Schema description coverage is 0% across 11 parameters with 4 required, so the description carries the full burden of explaining inputs and does not meet it. Only two phrases brush against parameters at all — 'Preserve unknowns' loosely maps to openQuestions and 'no technology or budget ceiling' to budgetContext/constraints — while title, businessOutcome, engagementType, requirements, existingSystems, timelineContext, acceptanceCriteria and procurementRequirements are given no meaning or format guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: it 'Formats confirmed business requirements for an RFP or proposal request', which is far more specific than the title. It also bounds scope negatively ('Does not store, transmit, quote or approve the project'), though it never names request_proposal as the downstream sibling an agent would otherwise confuse it with.

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 word 'confirmed' implies a prerequisite state (requirements must already be settled) and 'Preserve unknowns' hints at how to handle incomplete input, so usage is implied rather than stated. There is no explicit when-to-use/when-not-to-use guidance relative to request_proposal or get_procurement_information, leaving routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources