Skip to main content
Glama
theluckystrike

mcp-purchase-requisition

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
purchase-requisition_createA

Create a reusable purchase-requisition and return its CL-NNNN id: a name, a category and an optional description. Add steps with purchase-requisition_item_add. Free tier: 3 of them, runs unlimited.

purchase-requisition_item_addA

Add one step to a purchase-requisition and return its I01-style id: text, an optional section heading, and required flag. A required step left unanswered or failed blocks sign-off; an optional one does not.

purchase-requisition_item_removeA

Remove one step from a purchase-requisition by its I01-style id and bump the purchase-requisition version. Runs already under way keep the step they started with, so nothing anybody already ticked is rewritten.

purchase-requisition_showA

One purchase-requisition with its steps in order, grouped by section, plus how many are required and how many runs have been started from it. Pass as_text for a blank printable copy with a box against each step.

purchase-requisition_listA

Every purchase-requisition with its category, version, step count and how many runs came from it. Filter by category or by a word in the name. Returns at most 500 rows, newest change first.

purchase-requisition_deleteA

Delete a purchase-requisition and its steps for good. Runs already started keep their own copy of the steps and stay readable: deleting the purchase-requisition erases nothing anybody signed.

run_startA

Start a dated run of a purchase-requisition and return its RUN-YYYY-NNNN id. Steps are COPIED into the run, so editing the purchase-requisition later never changes a run under way. Runs are free, never capped.

run_checkA

Mark one step pass, fail or na, with who did it and when. na means the step did not apply; it counts as answered and never as passed. A step can be answered again while the run is open, and the last answer stands.

run_showA

The whole run: every step with its answer, who answered it and when, grouped by section, plus the pass, fail and outstanding counts, the failures in full, and whether it can be signed off and why not.

run_listA

Runs newest first, with their purchaseRequisition, progress and sign-off state. Filter by purchaseRequisition, by status, by reference or to open runs only. Returns at most 500 rows.

run_sign_offA

Sign off a completed run with a name and a date, which freezes it. Refused while a required step is unanswered or failed, unless force is true, and either way the exceptions stay on the record and print on the report.

run_statusA

Move a run back to open so a step can be answered again, or abandon it when the job did not happen. A signed-off run is refused: a signature is the point at which a run stops moving.

run_reportA

The run as plain text on every tier: every step with its mark, who answered it, the notes, the counts and a signature block or the recorded signature. Pro also writes it to out_path as a .txt file.

run_deleteA

Delete a run for good, with every answer on it. A signed-off run is refused: it is the record of what somebody put their name to. Abandon a run you no longer want instead of deleting a signed one.

license_statusA

Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.

license_activateA

Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.

Prompts

Interactive templates invoked by user choice

NameDescription
run_the_purchase-requisitionPick or build the purchaseRequisition, start a dated run against a job, answer every step with who and when, and sign it off with the exceptions on the record.

Resources

Contextual data attached and managed by the client

NameDescription
contractWhy a run copies its purchaseRequisition, the four item states and what na means, the run status machine, what blocks a sign-off, the free-tier limits and the one directory this server writes.

TDQS

A4/5.0

Scored across 16 tools

Disambiguation5/5

Each tool targets a distinct resource and action: template creation, item management, run lifecycle, and license management are clearly separated. Even similar-sounding tools like run_show and run_report are differentiated by purpose (interactive view vs. printable text export).

Naming Consistency4/5

Names mostly follow a predictable resource_action pattern, such as purchase-requisition_create, run_start, and license_activate. The pattern is slightly weakened by noun-like actions like run_status and license_status, where status means "change status" in one case and "report status" in the other.

Tool Count4/5

At 16 tools, the set is slightly above the ideal 3-15 range but still well-scoped for the domain: 6 template tools, 8 run tools, and 2 license tools. Each tool covers a recognizable operation, so the count feels reasonable rather than bloated.

Completeness4/5

The core lifecycle is well covered: create/show/list/delete requisitions, add/remove items, start/check/show/list/sign off/delete runs, and license management. Missing update operations for requisition metadata and item details are notable gaps, though they can be worked around by recreating or removing and re-adding items.

Maintenance

ActivityMaintained
ResponsivenessNo issues