Server definition
- Hash
- sha256:6af70ebbcb3da4c821c7d98cb856fe9150a9288710ea790984d61e88388212c7
- What it is
- What a remote MCP server returned when asked what it offers: 8 tools
The blob, as servednamed by its sha256
{
"instructions": "Methodology graph for project management, business and systems analysis (read-only, deterministic). Workflow: list_context → plan_project (compact) → plan_project for the current stage (full) → check_gate at each gate → validate_plan for a proposed plan. Every answer is an envelope {graph_version, data, warnings, errors}; errors carry did_you_mean. Cite link ids (Lxxxx) from explain_node. Verdicts are recommendations; people decide.",
"tools": [
{
"description": "Evaluates gate g.g0 … g.g10 against your evidence. Outcome precedence: Stop > Recycle > Hold > Conditional go > Go, with the rule that fired (outcome_reason). Critical evidence missing or stale → Hold; required non-critical missing, or a waiver without a reason or an approver who decides at this gate → Conditional go; a waiver with both → Go with the Waiver modifier (under regulation a waived critical artifact stays Conditional go until the deviation is recorded with the quality approval); optional gaps are notes. Modifiers: Work started without the gate, Overdue, Stale, Waiver. gate.deciders decide, gate.advisors take part. A disproved key product hypothesis is a Recycle, not a Stop: pass earlier_stage_invalid:true with invalid_stage:'st.discovery'. At G8 (go / no-go), work_started_beyond:true means production was changed before the decision: Hold (R3), not a Go with a modifier. Call without evidence to list what the gate needs. Returns a receipt hash of the inputs.",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"business_case_valid": {
"description": "false → Stop",
"type": "boolean"
},
"context": {
"additionalProperties": {},
"description": "Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.",
"properties": {
"ap": {
"description": "Delivery approach: predictive | agile | flow | hybrid",
"type": "string"
},
"bottleneck": {
"type": "boolean"
},
"con": {
"description": "Contract model: fixed | tm | capped | internal (own budget)",
"type": "string"
},
"data": {
"type": "boolean"
},
"date": {
"type": "boolean"
},
"dom": {
"description": "Project type: software | package | data | infra | process | nonit. package = SaaS / ERP / CRM platform; nonit = any non-IT project (a launch, a programme, an event, a move: add physical for works on site)",
"type": "string"
},
"high_stakes": {
"description": "A failure hits customers, money, safety or a regulated function: operational readiness and a rehearsed rollback at G8",
"type": "boolean"
},
"integ": {
"type": "boolean"
},
"legacy": {
"type": "boolean"
},
"migr": {
"type": "boolean"
},
"physical": {
"description": "Physical works in any domain: premises, construction, equipment or on-site events (an office move, a fit-out, an event on site). Adds the site inspection (G7), supplier contracts (G5), plan B with a fixed date and the permits note. A non-IT launch, programme or online event is dom=nonit without it",
"type": "boolean"
},
"reg": {
"type": "boolean"
},
"sc": {
"description": "Scale: single (one team) | multi (several teams)",
"type": "string"
},
"shared": {
"type": "boolean"
},
"size": {
"description": "Project size: solo | small | medium | large, default medium. solo = one person does all the work (small tailoring, no Daily Scrum or Kanban meeting); small ≈ up to 3 months and 5 people in one team; large ≈ several teams, over 12 months or a programme. Small and solo lower some gate documents one level (never under regulation) and drop the steering committee, large raises some",
"type": "string"
},
"svc": {
"type": "boolean"
},
"ui": {
"type": "boolean"
},
"unc": {
"description": "Uncertainty (complexity domain): clear | complicated | complex | chaotic",
"type": "string"
}
},
"type": "object"
},
"days_in_stage": {
"minimum": 0,
"type": "number"
},
"earlier_stage_invalid": {
"description": "true → Recycle; the answer names the stage to return to",
"type": "boolean"
},
"evidence": {
"additionalProperties": {
"anyOf": [
{
"description": "present | missing | stale | waived",
"maxLength": 20,
"type": "string"
},
{
"properties": {
"by": {
"maxLength": 200,
"type": "string"
},
"date": {
"maxLength": 40,
"type": "string"
},
"reason": {
"maxLength": 1000,
"type": "string"
},
"ref": {
"maxLength": 500,
"type": "string"
},
"state": {
"description": "present | missing | stale | waived",
"maxLength": 20,
"type": "string"
}
},
"required": [
"state"
],
"type": "object"
}
]
},
"description": "Map artifact id → state or {state, reason, ref, by, date}. A waiver is {state:'waived', reason, by}: by is the role id of a decider of this gate (see gate.deciders, e.g. r.client_owner) or 'name, role'. Unknown ids are reported as warnings with a suggestion.",
"propertyNames": {
"maxLength": 100,
"type": "string"
},
"type": "object"
},
"gate": {
"description": "Gate id, e.g. g.g5",
"maxLength": 40,
"type": "string"
},
"grace_days": {
"description": "Overrides both limits. Default: 80% of planned_stage_days, else by approach (predictive/hybrid 10, agile/flow 5); required evidence then waits twice as long",
"minimum": 0,
"type": "number"
},
"invalid_artifact": {
"description": "With earlier_stage_invalid: the artifact that is no longer true, to find where to return",
"maxLength": 100,
"type": "string"
},
"invalid_stage": {
"description": "With earlier_stage_invalid: the stage to return to, if known",
"maxLength": 100,
"type": "string"
},
"lang": {
"description": "Answer language, default en",
"enum": [
"en",
"ru"
],
"type": "string"
},
"planned_stage_days": {
"description": "Planned length of the stage in days. With it, missing critical evidence is overdue after 80% of it and missing required evidence after all of it",
"minimum": 0,
"type": "number"
},
"work_started_beyond": {
"description": "True if work of later stages already started (adds the 'work started without the gate' modifier; at G8 it is a Hold)",
"type": "boolean"
}
},
"required": [
"gate"
],
"type": "object"
},
"name": "check_gate",
"outputSchema": null
},
{
"description": "For a set of ids: antipatterns in the set and detected by rules, conflicts, redundant alternatives (e.g. seven estimation methods), items to avoid or not applicable here, risks, missing inputs and suggested additions. ok = no antipatterns, conflicts, avoid or not-applicable items; a detected pattern of severity warning (e.g. output over outcome on a client contract) does not change ok.",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"context": {
"additionalProperties": {},
"description": "Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.",
"properties": {
"ap": {
"description": "Delivery approach: predictive | agile | flow | hybrid",
"type": "string"
},
"bottleneck": {
"type": "boolean"
},
"con": {
"description": "Contract model: fixed | tm | capped | internal (own budget)",
"type": "string"
},
"data": {
"type": "boolean"
},
"date": {
"type": "boolean"
},
"dom": {
"description": "Project type: software | package | data | infra | process | nonit. package = SaaS / ERP / CRM platform; nonit = any non-IT project (a launch, a programme, an event, a move: add physical for works on site)",
"type": "string"
},
"high_stakes": {
"description": "A failure hits customers, money, safety or a regulated function: operational readiness and a rehearsed rollback at G8",
"type": "boolean"
},
"integ": {
"type": "boolean"
},
"legacy": {
"type": "boolean"
},
"migr": {
"type": "boolean"
},
"physical": {
"description": "Physical works in any domain: premises, construction, equipment or on-site events (an office move, a fit-out, an event on site). Adds the site inspection (G7), supplier contracts (G5), plan B with a fixed date and the permits note. A non-IT launch, programme or online event is dom=nonit without it",
"type": "boolean"
},
"reg": {
"type": "boolean"
},
"sc": {
"description": "Scale: single (one team) | multi (several teams)",
"type": "string"
},
"shared": {
"type": "boolean"
},
"size": {
"description": "Project size: solo | small | medium | large, default medium. solo = one person does all the work (small tailoring, no Daily Scrum or Kanban meeting); small ≈ up to 3 months and 5 people in one team; large ≈ several teams, over 12 months or a programme. Small and solo lower some gate documents one level (never under regulation) and drop the steering committee, large raises some",
"type": "string"
},
"svc": {
"type": "boolean"
},
"ui": {
"type": "boolean"
},
"unc": {
"description": "Uncertainty (complexity domain): clear | complicated | complex | chaotic",
"type": "string"
}
},
"type": "object"
},
"ids": {
"items": {
"maxLength": 100,
"type": "string"
},
"maxItems": 200,
"minItems": 1,
"type": "array"
},
"lang": {
"description": "Answer language, default en",
"enum": [
"en",
"ru"
],
"type": "string"
}
},
"required": [
"ids"
],
"type": "object"
},
"name": "check_mix",
"outputSchema": null
},
{
"description": "One node with its description, conditions, source, level and its links grouped by type, each with a link id (Lxxxx) to cite. Filter with link_types, direction and limit.",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"direction": {
"enum": [
"in",
"out",
"both"
],
"type": "string"
},
"id": {
"maxLength": 100,
"type": "string"
},
"lang": {
"description": "Answer language, default en",
"enum": [
"en",
"ru"
],
"type": "string"
},
"limit": {
"maximum": 500,
"minimum": 1,
"type": "integer"
},
"link_types": {
"items": {
"maxLength": 40,
"type": "string"
},
"maxItems": 30,
"type": "array"
}
},
"required": [
"id"
],
"type": "object"
},
"name": "explain_node",
"outputSchema": null
},
{
"description": "Call first. Returns the context dimensions and flags (with defaults and how many rules each flag drives), stages, gates, evidence states and levels, the gate outcome precedence and the suggested workflow.",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"lang": {
"description": "Answer language, default en",
"enum": [
"en",
"ru"
],
"type": "string"
}
},
"type": "object"
},
"name": "list_context",
"outputSchema": null
},
{
"description": "Route from presale to closure for a project context. Default is compact (ids by strength + a names dictionary, core items and gate evidence for all stages, about 6–10k characters). Ask for one stage with stages:['st.design'] and format:'full' for reasons, avoid texts and gate details. 'core' = do it here (context rule, flag or gate-critical artifact), at most 8 work items per stage (producers of the gate's critical artifacts first, then context rules, then flags).",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"context": {
"additionalProperties": {},
"description": "Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.",
"properties": {
"ap": {
"description": "Delivery approach: predictive | agile | flow | hybrid",
"type": "string"
},
"bottleneck": {
"type": "boolean"
},
"con": {
"description": "Contract model: fixed | tm | capped | internal (own budget)",
"type": "string"
},
"data": {
"type": "boolean"
},
"date": {
"type": "boolean"
},
"dom": {
"description": "Project type: software | package | data | infra | process | nonit. package = SaaS / ERP / CRM platform; nonit = any non-IT project (a launch, a programme, an event, a move: add physical for works on site)",
"type": "string"
},
"high_stakes": {
"description": "A failure hits customers, money, safety or a regulated function: operational readiness and a rehearsed rollback at G8",
"type": "boolean"
},
"integ": {
"type": "boolean"
},
"legacy": {
"type": "boolean"
},
"migr": {
"type": "boolean"
},
"physical": {
"description": "Physical works in any domain: premises, construction, equipment or on-site events (an office move, a fit-out, an event on site). Adds the site inspection (G7), supplier contracts (G5), plan B with a fixed date and the permits note. A non-IT launch, programme or online event is dom=nonit without it",
"type": "boolean"
},
"reg": {
"type": "boolean"
},
"sc": {
"description": "Scale: single (one team) | multi (several teams)",
"type": "string"
},
"shared": {
"type": "boolean"
},
"size": {
"description": "Project size: solo | small | medium | large, default medium. solo = one person does all the work (small tailoring, no Daily Scrum or Kanban meeting); small ≈ up to 3 months and 5 people in one team; large ≈ several teams, over 12 months or a programme. Small and solo lower some gate documents one level (never under regulation) and drop the steering committee, large raises some",
"type": "string"
},
"svc": {
"type": "boolean"
},
"ui": {
"type": "boolean"
},
"unc": {
"description": "Uncertainty (complexity domain): clear | complicated | complex | chaotic",
"type": "string"
}
},
"type": "object"
},
"format": {
"description": "Default compact",
"enum": [
"compact",
"full"
],
"type": "string"
},
"include": {
"description": "Default all four",
"items": {
"enum": [
"gates",
"avoid",
"notes",
"backbone"
],
"type": "string"
},
"type": "array"
},
"lang": {
"description": "Answer language, default en",
"enum": [
"en",
"ru"
],
"type": "string"
},
"min_strength": {
"description": "Default: core for all stages, all when stages are given",
"enum": [
"core",
"recommended",
"all"
],
"type": "string"
},
"stages": {
"description": "Stage ids or codes, e.g. ['st.analysis','design']. Default: all",
"items": {
"maxLength": 40,
"type": "string"
},
"maxItems": 20,
"type": "array"
}
},
"type": "object"
},
"name": "plan_project",
"outputSchema": null
},
{
"description": "Search names, ids, descriptions and aliases in English and Russian (word stems, small typos tolerated). Returns total and the best matches.",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"lang": {
"description": "Answer language, default en",
"enum": [
"en",
"ru"
],
"type": "string"
},
"limit": {
"maximum": 50,
"minimum": 1,
"type": "integer"
},
"query": {
"maxLength": 200,
"type": "string"
},
"type": {
"enum": [
"school",
"stage",
"gate",
"scenario",
"stream",
"event",
"practice",
"technique",
"model",
"artifact",
"tool",
"role",
"law",
"antipattern"
],
"type": "string"
}
},
"required": [
"query"
],
"type": "object"
},
"name": "search_graph",
"outputSchema": null
},
{
"description": "Checks an ordered list of steps (stages, gates, events, practices, techniques, notations, artifacts). Errors: empty plan, unknown ids, non-step types, stage order (analysis and design work planned early is only a warning 'early'; building before G3–G5 is an order error), contract after delivery gates, a gate after the step it authorises (G8 after the cutover), antipatterns, avoid or not-applicable items. Warnings: duplicates, redundant alternatives, early work, a cutover with no G8 or go / no-go meeting before it, antipatterns of severity warning. 'Shadow start' looks at the order: G4 or G5 must come before the first build step. 'expected' lists gate evidence not yet produced by earlier steps.",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"context": {
"additionalProperties": {},
"description": "Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.",
"properties": {
"ap": {
"description": "Delivery approach: predictive | agile | flow | hybrid",
"type": "string"
},
"bottleneck": {
"type": "boolean"
},
"con": {
"description": "Contract model: fixed | tm | capped | internal (own budget)",
"type": "string"
},
"data": {
"type": "boolean"
},
"date": {
"type": "boolean"
},
"dom": {
"description": "Project type: software | package | data | infra | process | nonit. package = SaaS / ERP / CRM platform; nonit = any non-IT project (a launch, a programme, an event, a move: add physical for works on site)",
"type": "string"
},
"high_stakes": {
"description": "A failure hits customers, money, safety or a regulated function: operational readiness and a rehearsed rollback at G8",
"type": "boolean"
},
"integ": {
"type": "boolean"
},
"legacy": {
"type": "boolean"
},
"migr": {
"type": "boolean"
},
"physical": {
"description": "Physical works in any domain: premises, construction, equipment or on-site events (an office move, a fit-out, an event on site). Adds the site inspection (G7), supplier contracts (G5), plan B with a fixed date and the permits note. A non-IT launch, programme or online event is dom=nonit without it",
"type": "boolean"
},
"reg": {
"type": "boolean"
},
"sc": {
"description": "Scale: single (one team) | multi (several teams)",
"type": "string"
},
"shared": {
"type": "boolean"
},
"size": {
"description": "Project size: solo | small | medium | large, default medium. solo = one person does all the work (small tailoring, no Daily Scrum or Kanban meeting); small ≈ up to 3 months and 5 people in one team; large ≈ several teams, over 12 months or a programme. Small and solo lower some gate documents one level (never under regulation) and drop the steering committee, large raises some",
"type": "string"
},
"svc": {
"type": "boolean"
},
"ui": {
"type": "boolean"
},
"unc": {
"description": "Uncertainty (complexity domain): clear | complicated | complex | chaotic",
"type": "string"
}
},
"type": "object"
},
"evidence": {
"additionalProperties": {
"enum": [
"present",
"missing",
"stale",
"waived"
],
"type": "string"
},
"description": "Artifacts that already exist",
"propertyNames": {
"maxLength": 100,
"type": "string"
},
"type": "object"
},
"lang": {
"description": "Answer language, default en",
"enum": [
"en",
"ru"
],
"type": "string"
},
"steps": {
"items": {
"maxLength": 100,
"type": "string"
},
"maxItems": 300,
"type": "array"
}
},
"required": [
"steps"
],
"type": "object"
},
"name": "validate_plan",
"outputSchema": null
},
{
"description": "For one event, practice, technique, notation, tool, artifact or antipattern: does it fit this context (fits / avoid / not_applicable / antipattern), its strength and why, alternatives and their group advice, risks, and which gates require it.",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"context": {
"additionalProperties": {},
"description": "Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.",
"properties": {
"ap": {
"description": "Delivery approach: predictive | agile | flow | hybrid",
"type": "string"
},
"bottleneck": {
"type": "boolean"
},
"con": {
"description": "Contract model: fixed | tm | capped | internal (own budget)",
"type": "string"
},
"data": {
"type": "boolean"
},
"date": {
"type": "boolean"
},
"dom": {
"description": "Project type: software | package | data | infra | process | nonit. package = SaaS / ERP / CRM platform; nonit = any non-IT project (a launch, a programme, an event, a move: add physical for works on site)",
"type": "string"
},
"high_stakes": {
"description": "A failure hits customers, money, safety or a regulated function: operational readiness and a rehearsed rollback at G8",
"type": "boolean"
},
"integ": {
"type": "boolean"
},
"legacy": {
"type": "boolean"
},
"migr": {
"type": "boolean"
},
"physical": {
"description": "Physical works in any domain: premises, construction, equipment or on-site events (an office move, a fit-out, an event on site). Adds the site inspection (G7), supplier contracts (G5), plan B with a fixed date and the permits note. A non-IT launch, programme or online event is dom=nonit without it",
"type": "boolean"
},
"reg": {
"type": "boolean"
},
"sc": {
"description": "Scale: single (one team) | multi (several teams)",
"type": "string"
},
"shared": {
"type": "boolean"
},
"size": {
"description": "Project size: solo | small | medium | large, default medium. solo = one person does all the work (small tailoring, no Daily Scrum or Kanban meeting); small ≈ up to 3 months and 5 people in one team; large ≈ several teams, over 12 months or a programme. Small and solo lower some gate documents one level (never under regulation) and drop the steering committee, large raises some",
"type": "string"
},
"svc": {
"type": "boolean"
},
"ui": {
"type": "boolean"
},
"unc": {
"description": "Uncertainty (complexity domain): clear | complicated | complex | chaotic",
"type": "string"
}
},
"type": "object"
},
"id": {
"description": "e.g. t.planning_poker, p.stage_gating, x.velocity_kpi",
"maxLength": 100,
"type": "string"
},
"lang": {
"description": "Answer language, default en",
"enum": [
"en",
"ru"
],
"type": "string"
}
},
"required": [
"id"
],
"type": "object"
},
"name": "when_to_use",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:6af70ebbcb3da4c821c7d98cb856fe9150a9288710ea790984d61e88388212c7 | sha256sum