@ateam-ai/mcp 0.4.83 → 0.4.84

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/tools.js +12 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ateam-ai/mcp",
3
- "version": "0.4.83",
3
+ "version": "0.4.84",
4
4
  "mcpName": "io.github.ariekogan/ateam-mcp",
5
5
  "description": "A-Team MCP Server — build, validate, and deploy multi-agent solutions from any AI environment",
6
6
  "type": "module",
package/src/tools.js CHANGED
@@ -3129,6 +3129,18 @@ const handlers = {
3129
3129
  design_advisor: {
3130
3130
  _important: "BEFORE and WHILE you design any skill/solution you MUST consult ateam_design_advisor. You do NOT know which platform capabilities exist or when to use them — the advisor does. Describe your goal to it and it returns pointers to the right capabilities (per-actor storage, widgets, triggers, sub-agents, mobile data, run-scripts, multi-skill handoff, GitHub, …) with the /spec topic to read next and the tool to wire each. It's advisory — you decide and own the design — but skipping it means you'll miss capabilities the platform already provides.",
3131
3131
  how: "ateam_design_advisor({ goal: '<what you are building, in your words>', design_state: {} }). Re-call it as the design evolves (pass the current design_state) to get 'what's still missing' hints. Then ateam_get_spec(topic) for any capability it points you to. For anything deeper — details, examples, or topics outside the capability list — ateam_spec_search({ query: '<how do I…>' }) does a semantic search over the FULL spec docs.",
3132
+ // A MANDATE WITH NO FALLBACK IS A SINGLE POINT OF FAILURE, and it failed:
3133
+ // on 2026-09-04 the advisor errored three times for one design and the
3134
+ // agent, told to consult it and given nowhere else to go, fell back to
3135
+ // reading whichever spec topic happened to mention the thing it wanted —
3136
+ // and concluded a capability was absent that had shipped. Name the other
3137
+ // doors here, at the point where the obligation is stated.
3138
+ if_the_advisor_does_not_answer:
3139
+ "It is not the only door and you are NOT stuck. ateam_get_spec(topic:'device-capabilities') is the GENERATED " +
3140
+ "capability matrix (what the phone can do, per API, with status) and ateam_spec_search({query}) searches the full " +
3141
+ "spec corpus — neither has an LLM in the path, so neither fails the way the advisor can. If the advisor answers " +
3142
+ "with `truncated: true`, what you got is CORRECT but INCOMPLETE: use it, and treat a capability's absence as " +
3143
+ "UNKNOWN rather than 'no' — re-ask with a narrower goal, or check the two tools above.",
3132
3144
  },
3133
3145
  what_is_a_team: {
3134
3146
  definition: "A Team is a structured multi-role AI system composed of Skills, Connectors, Governance contracts, and Managed Runtime deployment.",